Alan Cox wrote:
> But try 2.4.1 before worrying too much. That fixed a lot of the block
> performance problems I was seeing (2.4.1 ruins the VM performance under paging
> loads but the I/O speed is fixed ;))

---
        Seems to have gotten a bit worse.  Vmstat output after 'vmware' had completed
write -- but system unresponsive and writing out a 155M file...

 1  0  0      0 113960  47528 277152   0   0     0     0  397   861   1  24  75
 1  0  0      0 114060  47560 277152   0   0     4   350  432  1435   4  17  79
 0  0  1      0 127380  47560 266196   0   0     0   516  216   435   7   3  90
 1  0  1      0 127380  47560 266196   0   0     0   240  203   173   0   1  99
 0  0  1      0 127380  47560 266196   0   0     0   434  275   180   0   2  98
 1  0  1      0 127376  47560 266196   0   0     0   218  204   173   0   2  98
 0  0  1      0 127376  47560 266196   0   0     0   288  203   174   0   0 100
 0  0  1      0 127376  47560 266196   0   0     0   337  230   176   0   1  99
 0  0  1      0 127376  47560 266196   0   0     0   267  241   177   0   1  99
 0  0  1      0 127376  47560 266196   0   0     0   210  204   173   0   1  99
 0  0  1      0 127376  47560 266196   0   0     0   204  203   173   0   1  99
 0  0  1      0 127376  47560 266196   0   0     0   216  212   250   0   1  99
 0  0  1      0 127376  47560 266196   0   0     0   208  205   172   0   2  98
 0  0  1      0 127372  47560 266196   0   0     0   225  203   160   0   2  98
 0  0  1      0 127372  47560 266196   0   0     0   316  214   212   0   1  99
 1  0  1      0 127144  47560 266196   0   0     0   281  218   304   1   2  96
 0  0  0      0 127144  47560 266196   0   0     0     1  161   240   1   0  99
 0  0  0      0 127144  47560 266196   0   0     0     0  101   232   0   1  99 
---
        What is the meaning of having a process in the 'w' column?  On other
systems, I was used to that meaning an executable had been *swapped* out completely
(as opposed to no pages mapped in) and that it meant your system vm was 'thrashing'.
But that obviously isn't the case here.

        Those columns are output from a 'vmstat 5'.  Meaning it took about 70 seconds
to write out 158M.  Or about 2.2M/s.  That's probably not bad.  It still locks
up the system for over a minute though -- which is really undesirable performance
for interactive use.  I'm guessing the vmstat output numbers are showing 4K? 8K? 
blocks?  8K would about make sense for the 2.2M average.

-- 
Linda A Walsh                    | Trust Technology, Core Linux, SGI
[EMAIL PROTECTED]                      | Voice: (650) 933-5338
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Reply via email to