Re: Looking for the cause of poor I/O performance

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> throughput. I'm hoping that this still may be related to some sort of PCI 
> latency issue.

you can use setpci to do this sort of tweaking.  naturally,
you probably want to mount your filesystems RO when you do this,
since accidents do happen...

but in abstract, it's quite odd to believe that you can persuade a 
7-year old machine to perform as well as a current one.  sure, it 
sometimes happens, but so very much has changed.  as a completely
random example, the topology of bus-like links in a modern box is 
vastly less bottlenecked than in the bad old days.  for instance,
it was completely normal back then for the chipset's builtin IDE
(and any add-ons) to sit on a single 32x33 PCI segment.  that segment
was often unable to actually approach 133 MB/s (80 was pretty good 
in those days).  and often vendors would bend the rules a little
like adding a bit more delay in arbitration in order to permit
more PCI slots (since PCI, like any multidrop bus, always has a 
speed-drops tradeoff). 

nowadays, it's actually common to see unshared pcix slots direct
to a memory-controller-hub, along with unshared connections for 
*ATA, sound, even ethernet.  not to mention the fact that memory
itself is 10x faster.

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux