Bug 134538 - Enormous amount of disk activity upon login
Summary: Enormous amount of disk activity upon login
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-desktop
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-04 14:59 UTC by Mikael Carneholm
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-10-04 15:20:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mikael Carneholm 2004-10-04 14:59:52 UTC
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.

Suggestion:
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 15:20:03 UTC
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.