C
ChUIMonster
Guest
FWIW loading data is not typically something that -B is going to help with. In a load focused scenario there is much less benefit to caching -- your "hit ratio" is quite low. That doesn't directly explain why things get slower but I would not have expected much benefit in that scenario to start with. I *suspect* that you are seeing behavior related to the allocation of memory for -B. My guess is that there is some sort of lazy memory allocation going on -- the OS (or the VM -- is this a virtual environment?) isn't allocating all of the RAM when it is asked for but is instead trickling it out on demand and maybe having an increasingly difficult time arranging for those additions or rearranging things to fit within the address space or something like that. The big benefit from "bigger is better" -B thinking is tied to *reads*. Most applications are much, much heavier readers than they are writers. And "locality of reference" is very strong in most application's read activity (the same stuff gets read over and over and over... again and again and again...) I think you should dig into that windows problem that was referenced above. Or, if this is a VM, look at the memory allocation settings.
Continue reading...
Continue reading...