1) this setting is only good for win98, 95 not XP or 2000
2) It sets aside a buffer in memory for disk i/o. If a file is read or opened from disk, the OS will maintain this area as a place to look for file data, so it doesnt have to make the expensive and slow process of going out to disk to get information.
3) In a normal situation, such as a database, this would make perfect sense. However, giga and some DAw software have their own caching mechanism, so a) this wastes memory by double buffering the same information b) this can waste processing time.
So, given this, its best to let giga handle caching by giving it more memory to play with, and lowering teh system cache. Also, it will give giga more memory to load more sounds
16384 is about right. Various low settings have been tried but this setting has been proven to be the best case by most people. systems vary of course, so you can experiment a bit with the actual number...but its a good start. Some people set this to 2048, but performance may be worse all around...
This is the one common optimization I havent tweaked yet - being still quite new to GSt, just a few months using a Win98se PC. Here\'s my question about VCache! When I go in there I find that I have NO VCache ENTRY at all! Nada. Blank. Should I just type it in? The optimization guides all suggest \"changing\" your VCache to such and such a pair of numbers. But if mine is blank and GSt seems to be running fine (no pops or clicks and good polyphony) I wonder what this means?