![](https://seccdn.libravatar.org/avatar/cabdbf4d350ab6a15265803acab1634d.jpg?s=120&d=mm&r=g)
Per Jessen said the following on 06/13/2011 08:08 AM:
But if they are holding session-specific data then WHY? Why not keep it in mapped/paged memory?
More wild guessing - because it needs survive a crash?
Possibly. In some cases. But not all, surely?
If it is a per session cache for the application and needs retrieval, then its a candidate for fast storage, isn't it?
Perhaps - but it's already cached by the filesystem buffers.
Which gets back to my original question ... And of course the general cure to Linux performance issues: throw more memory at it! Sadly there is a lower limit with laptops and netbooks than with desktops and servers. -- Security is old, older than computers And old-guard security thinks of countermeasures as a way to manage risk. Avoiding threat is black & white, either you avoid it or you don't. Managing risk is continuous. - B Schneier, "Secrets and Lies" pp 385 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org