Quote:
Originally Posted by Xitix
Your clueless. For a file under 4k in size Vanguard is doing 66 reads including a 4k read right at the start which reads in the ENTIRE FILE. It repeats the same shitty pattern for every sound and music .ICB file it opens. It also opens and reads the .ICB files fully then closes them before it starts playing any sound from the matching .ISB file. So it has nothing to do with streaming and everything to do with real crap code paths for first opening the sound files. It also does the same thing when it reads parts of the .ISB file - rereading what it just read over and over again.

There are two distinct access patterns for asset files in VG. One is when they are first opened and the structure/directory information of whats in the file and where is read. The second is randomly retrieving/streaming specific assets from the file as needed. For sound files the first is absolute gargage currently. For other assets I don't know but suspect they might have some problems as well. For the second way when files are being read mostly in sequence anyway (like the sound files are) loading in decent sized chunks will be faster, at least all 8k chunks and not 8k,512bytes,8k,512bytes etc.

As for this being a performance hit, it sure is but as to the degree I don't have the rest of the code to profile so can't say. Still this isn't an optmization issue - it's getting rid of redundant unneccesarry reads and any performance gain will happen exactly where a lot complain VG peforms poorly: when new stuff is being loaded.

This is not a dead issue by the way, I am still trying to get people to look further into this.</div> <div> __________________
Nino McHammer
Fires of Heaven
Veeshan

Weiterlesen...