I'd wager that the poor performance is the combination of updatedb running and having only 256MB of RAM. Updatedb is creating a lot of IO and consuming a fair amount of RAM, possibly causing swap, which in turn creates more IO, which hurts the performance of the system. I'm not sure of the best way to handle this, especially not as a "bug", given that it seems as if your computer is simply being asked to do more than it can easily handle, and is slowing down as a result. Disabling updatedb is the "obvious" solution, but that will have some unintended consequences. This thread in the forums talks about disabling it, which should serve as a starting point for you, though I don't recommend disabling the running of updatedb. http://ubuntuforums.org/showthread.php?t=6279
Perhaps setting updatedb to run weekly instead of daily would be a good middle ground? if you move the "slocate" and "find.notslocate" files in "/etc/cron.daily" to "/etc/cron.weekly" that will make it run less often and should alleviate the problem. On 8/27/07, John Vivirito <[EMAIL PROTECTED]> wrote: > > Yes it was running at boot time as it did before, its the only thing i > can link to the issue > > P4 1.7ghz > 256mb ram > 40 gig hd with gutsy > > -- > [Gutsy] after this mornings updates gnome took >5minutes to load > https://bugs.launchpad.net/bugs/129928 > You received this bug notification because you are a direct subscriber > of the bug. > -- -Regards- -Quentin Hartman- -- [Gutsy] after this mornings updates gnome took >5minutes to load https://bugs.launchpad.net/bugs/129928 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
