https://bugzilla.novell.com/show_bug.cgi?id=625339
https://bugzilla.novell.com/show_bug.cgi?id=625339#c79
--- Comment #79 from Richard Creighton
Does increasing the hardlock limit as described below help?
http://forums.opensuse.org/english/information-new-users/unreviewed-how-faq/...
On 2010-10-14 Vadim Krevs offered the following:
https://bugzilla.novell.com/show_bug.cgi?id=625339
https://bugzilla.novell.com/show_bug.cgi?id=625339#c78
--- Comment #78 from Vadim Krevs
2010-10-14 16:25:43 UTC --- Does increasing the hardlock limit as described below help? http://forums.opensuse.org/english/information-new-users/unreviewed-how-faq /447481-hardlocklimit-256-11-3-install-default-may-cause-open-office-issues .html
I was unaware of this thread, however, I came to the same conclusion as the posters, the LOCKS limits were/are too low. They seem to be set at @256 by default which is probably based upon a default memory of 512k or possibly 1G. However, I have 3G and many people have even more and I think that setting is probably low so when people start running KDE or other DE's that allow multiple screens and multi-tasking operations routinely and many of these tasks launch multiple threads you are going to run out of 'room' for processes and have to start locking (read waiting) for things to finish up before new things can launch or things that were sleeping can be reawakened and resumed. So, things like updating screens get delays because they are put on hold. Well, most machines have the memory and horsepower to handle more than 256 job/threads/memory requirements at once so don't need to be locked down so tightly IMO, so I raised the limit on my machine to 2048 Hardlimit and 512 softlimit both with @ which makes it an absolute limit in Kbytes rather than a % of memory "Limit the size of the memory that a single process may lock in physical memory (thus preventing it to be swapped out). Hard limit: Can not be increased by non-root. This value corresponds to ulimit -Hl Parameter is in percent of physical memory (unless you prefix it by @, in which case it means kilobytes), 0 means no adjustment." It has helped a lot and the problem is virtually gone unless my system is really overloaded, like when both cpu cores are at 100% and disk I/O is high and it is starting to use swap space and I'm running SVN refreshing the sources for KDE or some such. Then, I still notice some pauses, but when svn isn't running, I rarely notice any like I used to. Before, I would get 5-6 second delays every time KMail checked for mail on one of my various mail sources, which was every few minutes to one or another, but now, is very rare that I ever notice even a half second, if that. FWIW, my system is a homebrew Athelon dual core cpu w/32 bit 11.3 Suse running 2.6.35 and KDE 4.5.2 with 3G ram, 2TB in a raid5 array w/2 additional drives in a LVM and a couple of USB 1TB drives hooked on for diddling around and backups. This is tied into a wireless LAN talking to my big machine in the living room which has a 5TB raid5 and a 1TB raid5 and a SMC 8 port router tied into the other wireless and 2 other machines, one of which is my mail and www server and the other is my test machine that I do most of my beta testing on. I used to teach Linux in college, but since my stroke, I can't do that anymore so me and my cat mostly just enjoy puttering with what I *used* to be able to do efficiently and try and remember "how it used to be" and occasionally I still find something useful to do <grin>. Hopefully, something good will come from all of this. I do believe this 'pausing' issue is a scheduling problem because SuSE 10.3 -11.1 didn't seem to have this problem on the same machines with the same memory resources, but the new kernels and new DE's and applications have changed so radically and grown so complex that I don't think that all the "engineers" at Fort Bill Gates" could do any worse at screwing it up <grin>. Thankfully, with Linux, there is the labor of love of thousands working on it rather than the greed of a few hundred butchering it. Richard -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.