Bug 134538 - Enormous amount of disk activity upon login
Enormous amount of disk activity upon login
Product: Fedora
Classification: Fedora
Component: gnome-desktop (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mark McLoughlin
Depends On:
  Show dependency treegraph
Reported: 2004-10-04 10:59 EDT by Mikael Carneholm
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-04 11:20:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mikael Carneholm 2004-10-04 10:59:52 EDT
Description of problem:
The summary says it all, really...there is a tremendous amount of disk
activity going on when loggin in to a gnome desktop. When using a
product by a certain redmond-based company there is no such activity,
and the login process is thus much faster (and quieter) on that product.

Something has to be done in this area. Maybe a common binary file
could be used by all gnome applications for storing settings etc,
resulting in only one diskread operation? Or maybe forcing
applications to abandon custom .foo files and use gconf instead? Just
some ideas.
Comment 1 Mark McLoughlin 2004-10-04 11:20:03 EDT
Its a known issue, work has been done in the area and more work needs
to be done. One example is the use of readahead(2) in order to
pre-cache the files which we'll use on login.

However, there's not much use in keeping this bug open - especially
against this package:

  The gnome-desktop package contains an internal library
  (libgnomedesktop) used to implement some portions of the GNOME
  desktop, and also some data files and other shared components of the
  GNOME user environment.

What we really need is targetted profiling of the disk activity and
specific bugs logged on areas which can actually be fixed.

Thanks for taking the time to log the bug, though

Note You need to log in before you can comment on or make changes to this bug.