| Arno Wagner 2007-04-02, 1:14 pm |
| In comp.sys.ibm.pc.hardware.storage markm75 <markm75c@msn.com> wrote:
> On Apr 1, 10:27 am, "markm75" <markm...@msn.com> wrote:
[vbcol=seagreen]
> Very very bad results with max compression, took like 12 or 13
> hours...
> This baffles me.. as I know that I can do the backup on the same drive
> locally in 4 hours on that machine..
With maximum compression? Ok, then it is not a CPU issue.
> and I know I can do the same type
> backup on the remote (destination) as well.. so going from D on
> ServerA to E on ServerB should just be a limitation of the network,
> which benches at 60 MB/s in all of my tests.
There seems to be some problem with the network. One test you can try is
pushing, say, 10 GB or so of data through the network to the target
drive and see how long that takes. If that works with expected speed,
then there is some issue with the type of traffic your software
generates. Difficult to debug without sniffing the traffic.
One other thing you shoulkd do is to create some test setup, that
allows you to test the speed in 5-10 minutes, otherwise this
will literally take forever to figure out.
> Again, I dont think jumbo frames would help.. but I cant even turn
> them on , as each nic on each end doesnt have this setting, not sure
> what else to test here or fix.
I agree that jumbo-frames are not the issue. They can increase
throughput by 10% or so, but your problem is an order of magnitude
bigger.
Here is an additional test: Connect the two computers directly with
a short CAT5e cable and see whether things get fater then.
Arno
|