Locking physical memory on NT based OSes

In reference to my previous topic:

http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=show&ixPost=94904&ixReplies=20

I colleague of mine pointed me to this:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/memory/base/address_windowing_extensions.asp

I was considering the problem, and I realized there is no way SQL server could be putting out the kind of performance numbers it has w/ out something like this.  Sure enough, there are many articles on tuning AWE and SQL Server. 

This is giving me more confidence in the single threaded server approach.  If performance is a concern, I'll lock pages.  There really isn't an excuse to run a server low on RAM anyway. 

Merry Christmas
~christopher

christopher baus (www.baus.net)
Wednesday, December 24, 2003

Opps...  I realized that it applies to the 32bit+ memory addressing extensions.  Feel free to kill the thread.  I'm still looking for a solution.

christopher baus (www.baus.net)
Wednesday, December 24, 2003

Maybe this has already been suggested: you may want to consult “Programming Applications for Microsoft Windows” by Jeffrey Richter. Even though the book title does not suggest this, actually the book explains the win32 internals in a very straight language. It allocates huge spaces to the internals of win32 threading, memory architecture, memory mapped files, paging and other goodies. If the page faults are causing you problems I don't know of any better place to look for a solution.

coresi
Thursday, December 25, 2003

  Recent Topics

  Fog Creek Home