Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Best practice for production servers: To reboot or not to reboot?



Some high performance database engines wire their cache (ex: Cach?).  Virtual machine monitors wire portions of the memory that they manage (ex: VMware Fusion, probably VMware Workstation but I don't have it handy to see).  Some Java VMs wire their heap allocations (ex: Java HotSpot VM), which is why I brought it up in the first place.

There's a lot more wired memory in use out there than you suspect, I think.  Few apps wire all of their memory allocations but many wire the slabs critical to performance.

--Rich P.









BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org