Updates:
        Status: Invalid

Comment #5 on issue 20821 by [email protected]: fs_usage shows that Chrome  
is reading and writing on the disk several times every second.
http://code.google.com/p/chromium/issues/detail?id=20821

It's not "several times every second". When Chromium is sitting idle with  
no user
interaction, it hits the disk every 30s.

If we use the commandline:
sudo fs_usage -w -f filesys Chromium

We see on idle:

11:14:13.303  write             F=13   B=0x1
                                                         0.000013   Chromium
11:14:13.303  read              F=12   B=0x1
                                                         0.000004   Chromium
11:14:43.303  write             F=13   B=0x1
                                                         0.000011   Chromium
11:14:43.303  read              F=12   B=0x1
                                                         0.000004   Chromium
11:15:13.303  write             F=13   B=0x1
                                                         0.000012   Chromium
11:15:13.303  read              F=12   B=0x1
                                                         0.000004   Chromium

When we move the mouse around, we are pounding fds 12 and 13 quite a bit:

11:13:16.628  read              F=12   B=0x1
                                                         0.000005   Chromium
11:13:16.645  write             F=13   B=0x1
                                                         0.000018   Chromium
11:13:16.645  read              F=12   B=0x1
                                                         0.000004   Chromium
11:13:16.662  write             F=13   B=0x1
                                                         0.000015   Chromium
11:13:16.662  read              F=12   B=0x1
                                                         0.000004   Chromium
11:13:16.679  write             F=13   B=0x1
                                                         0.000009   Chromium
11:13:16.679  read              F=12   B=0x1
                                                         0.000003   Chromium
11:13:16.695  write             F=13   B=0x1
                                                         0.000008   Chromium
11:13:16.695  read              F=12   B=0x1
                                                         0.000003   Chromium
11:13:16.712  write             F=13   B=0x1
                                                         0.000010   Chromium
11:13:16.712  read              F=12   B=0x1
                                                         0.000004   Chromium
11:13:16.729  write             F=13   B=0x1
                                                         0.000009   Chromium
11:13:16.729  read              F=12   B=0x1
                                                         0.000004   Chromium

What are fd 12 and 13? lsof says:

Chromium  82403  avi    8     PIPE 0x8738ce8     16384
Chromium  82403  avi    9     PIPE 0x85554b8     16384
Chromium  82403  avi   10r     CHR       8,1     0t240 141354372  
/dev/urandom
Chromium  82403  avi   11u  KQUEUE                               count=0,  
state=0x2
Chromium  82403  avi   12     PIPE 0xccc2ce8     16384
Chromium  82403  avi   13     PIPE 0xccc3328     16384
Chromium  82403  avi   14u    unix 0xa2d5770       0t0           ->0xd71e4c8
Chromium  82403  avi   15u     REG      14,2         8  31630356
/private/var/folders/zz/zzzivhrRnAmviuee++-HUU++Is6/-Tmp-/org.chromium.5q2xSB

This "hammering" of the disk is really IPC activity which counts as  
filesystem
activity for the purposes of fs_usage.

Case closed.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to