SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
SI - Site Forums : Silicon Investor - Legacy Interface Discussion (2004-2011) -- Ignore unavailable to you. Want to Upgrade?

To: SI Dave who wrote (2728)11/30/2004 6:23:59 PM
From: SI Bob  Respond to of 6035
 
Yeah. Windoze insists on making a lot of virtual memory on the drives, but doesn't use half the physical memory? And it knows the memory's there and I'm almost positive I've got everything set up to tell it and SQL Server to have at it.

I have zero doubt that if it cached all reads until memory was full, the cache would be full in a few weeks at most.

Well, I just started the performance monitor and hopefully I've added the right counters.

SQL Server's Buffer cache hit ratio is right at 99.743% right now. But the one called just "Cache Hit Ratio" is running more like 89.9%.



To: SI Dave who wrote (2728)11/30/2004 6:31:23 PM
From: SI Bob  Read Replies (2) | Respond to of 6035
 
67% file fragmentation sound a little on the high side? hehe

Also, it looks like the swap file size is 2 gig. I've always been told you should just let Windoze do what it thinks is best, but it sure is tempting to force it not to use a swap file and see what happens. According to the performance monitor, usage of it is at 0.693% right now. I don't see why it's using any of it when there's 4.8 gig of memory available.


HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2026 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News