Comment 8 for bug 208552

nire wrote:
> Vista <- Server: Peak speed is ~ 5 MB/s. The speed is decreasing until the recieving is finished. Stops at 1,1 MB/s

Okay, for one thing, you should wrap the copy with "time" on Linux, or
something equivalent on Windows. Relying on the program's running
tally of throughput isn't a good idea when benchmarking. Take your
700MB file, and divide that by the total time to transfer (70 seconds,
say), and get your 10MB/s rate. Repeat that a few times, and average
it together, looking for any extreme outliers.

So copying over SSH, you're getting...
> Ubuntu -> Server: 1,9 MB/s
> Vista -> Server: 5,2-5,4 MB/s

And copying over Samba, you're getting:
Client (Ubuntu 8.04) -> Server Never above 3,7 MB/s
Client (Vista) -> Server ~12 MB/s

So the interesting thing to me here is that this doesn't really seem
like a Samba issue here. By these numbers, I think you're saying that
it takes 2-3 times as long to send the same large file from the same
laptop running Hardy vs Vista, to the same server running Ubuntu? And
you've run this repeatedly, with the same file, same hardware, just
different OS (Hardy vs Vista)?

If that's true, I think we're dealing with something more fundamental
to the networking stack and probably your ethernet driver.

> Ubuntu -> Server: The transmit never starts actually.. It stands on 0 byte until you force it to quit.

What happened here?

> Ubuntu <- Server: 7-8 MB/s
> Vista <- Server: 2,3 MB/s

This result is puzzling, and not consistent with the rest of your
stats. In this one case, the network transfer to Ubuntu outperforms
Vista by 2-3 times. Hmm.

In any of these cases you might have caching issues, where you send a
file from one machine to another, delete it, then try to send again
and it's been cached in memory somewhere, either on the client or
server.

So from these results, I'd tend to conclude that this isn't a
Samba-specific issue, that it's something more networking related. To
debug that, you're going to need some more scientific network
benchmarking tools. I recommend installing the dbench package
(written by one of the samba authors, cooincidently), and using the
tbench utility. You'll need it on both the client and the server.
You'll run "tbench_srv" on the server. And then you'll run something
like "tbench -t 60 SERVER_IP" on the client.

See:
http://samba.org/ftp/tridge/dbench/README

:-Dustin