Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: hate to break it to ya (Score 1) 357

by sean.k (#1993320) Attached to: Kernel Musings: Unix and NT
but SQL Server is configured to seize a specific amount of RAM at bootup. I think it defaults to 64, though it may be higher. This is where the huge RAM hit is coming from. And if you think about it, giving an SQL server a bunch of RAM initially makes more sense than having it request more every time someone runs a query. Personally, my SQL servers are all dedicated machines. You may not notice a performance degradation with a web server until it gets busy but a single complex query and you'll be doing anything you can for a few extra CPU cycles :)

"Mach was the greatest intellectual fraud in the last ten years." "What about X?" "I said `intellectual'." ;login, 9/1990

Working...