Thought you might find this worth reading since it is on topic to this
thread:
http://techreport.com/reviews/2006q3/maxtor-diamondmax-11/index.x?pg=6
Mark Smith wrote:
Mark Smith wrote:
Actually, setting SNDBUF and RCVBUF to 65536 from the default of 8192
is what got me _TO_ 22MBps...
In the interest of closing this loop for the sake of the archives... :)
My company has officially thrown in the towel on this issue. Everything
we're seeing is suggesting that 22MBps is about as fast as we're going
to get with SMB. RedHat, our parent company's IT department (much
bigger
Doug VanLeuven wrote:
Mark Smith wrote:
I also tried your values, with the tcp_window_scaling, with no luck.
It's enable by default, but I explicitly set options other options
depend on.
Reasonable idea. :)
I set up my test rig again.
Host server
2.6.12-1.1376_FC3, samba 3.0.23
Broadcom
Guenter Kukkukk wrote:
Hi Doug,
have you ever tried netio to check for raw needwork speed?
http://www.ars.de/ars/ars.nsf/docs/netio
It does not add any overhead caused by file operations - so it
can help to tune raw parameters.
The source is included - so it can be tuned, too.
When sniffing
Mark Smith wrote:
Actually, setting SNDBUF and RCVBUF to 65536 from the default of 8192 is
what got me _TO_ 22MBps...
...Ya know, I once tried increasing SNDBUF and RCVBUF to 256k but didn't
see any difference. I've also tried setting the kernel parameters to
256k, but never both at the
Mark Smith wrote:
I also tried your values, with the tcp_window_scaling, with no luck.
It's enable by default, but I explicitly set options other options
depend on.
I set up my test rig again.
Host server
2.6.12-1.1376_FC3, samba 3.0.23
Broadcom Nextreme BCM5702X Gigabit, tg3 driver default
On Saturday 23 September 2006 17:13, Doug VanLeuven wrote:
Mark Smith wrote:
I also tried your values, with the tcp_window_scaling, with no luck.
It's enable by default, but I explicitly set options other options
depend on.
I set up my test rig again.
Host server
2.6.12-1.1376_FC3, samba
OK, I'll top post.
I can't let this stand unanswered.
I ran a LOT of tests with gigabit copper and windows machines. I never
did better than 40 seconds per gig. That was with the Intel cards
configured for maximum cpu utilization. 80-90% cpu for 40 sec per gig.
On windows. Uploads went
Doug VanLeuven wrote:
OK, I'll top post.
I can't let this stand unanswered.
I ran a LOT of tests with gigabit copper and windows machines. I never
did better than 40 seconds per gig. That was with the Intel cards
configured for maximum cpu utilization. 80-90% cpu for 40 sec per gig.
On
Mark Smith wrote:
As a data point, I'm going to try a newer version of Samba. (RHEL4 uses
3.0.10-RedHat-Heavily-Modified-Of-Course) If that makes a difference,
then I have to decide whether it's worth it to me to keep RedHat support
or not. (And when I say I, I really mean my management.)
I have not. Unfortunately, that is not a trivial process. I believe
everything supports it, but it's a somewhat major change to my
production systems. It might be worth trying as a data point, however.
Given the iPerf tests, I really don't think it's a network bottleneck at
this point.
i am not an expert, but,
do you have jumbo frame enabled on your nic and switch?
try using ethtools...
RP
Mark Smith wrote:
Mark Smith wrote:
As a data point, I'm going to try a newer version of Samba. (RHEL4
uses 3.0.10-RedHat-Heavily-Modified-Of-Course) If that makes a
difference, then
I wanted to follow up to my email to provide at least a partial answer
to my problem.
The stock RedHat AS4-U3 Samba config has SO_SNDBUF and SO_RCVBUF set to
8k. With this value, I can transfer a 1GB file in about 70-75 seconds,
about 14MBps. If I increase those buffers to their max value
We use SMB to transfer large files (between 1GB and 5GB) from RedHat AS4
Content Storage servers to Windows clients with 6 DVD burners and
robotic arms and other cool gadgets. The servers used to be Windows
based, but we're migrating to RedHat for a host of reasons.
Unfortunately, the RedHat
On Tue, Sep 19, 2006 at 06:19:43PM -0700, Mark Smith wrote:
We use SMB to transfer large files (between 1GB and 5GB) from RedHat AS4
Content Storage servers to Windows clients with 6 DVD burners and
robotic arms and other cool gadgets. The servers used to be Windows
based, but we're
Jeremy Allison wrote:
An interesting thing you could do is to use a port of smbclient
on Windows (no I don't know where to get one :-) to copy the
client to the Windows client in userspace. smbclient will use
read pipelining (ie. issue more than one read at a time) whereas
Windows clients issue
16 matches
Mail list logo
