I am looking for examples regarding AsyncReadManager.Read to read multiple files from within a burst job.
What is the idea/concept/benefit of using multiple ReadCommands vs a single large read command in AsyncreadManager.Read? Was designed with having one large database file in mind and maintaining all indices/offsets within this file our own and then working on subranges within this file?
How to effiicently load multiple files with AsyncReadManager?
Is FixedString{Size} the correct new string struct to be used to pass the file path into a bursted job?
When streaming entity binary files we want to stream directly into the chunks. Those might not have contiguous memory addresses. Thus we will read a file linearly but with multiple read commands.
Larger read commands are always better, wherever that is possible.