Operation:
dd if=/dev/zero of=test bs=16384 count=512
Results:
(CIFS)
8388608 bytes (8.4 MB) copied, 1.7191 s, 4.9 MB/s
(NFS)
8388608 bytes (8.4 MB) copied, 0.852603 s, 9.8 MB/s
what's the problem? what is the expected result? what caught your
attention?
cifs and nfs are very
I would expect both protocols to saturate the network. What are your
performance expectations for cifs?
CIFS performance is not limited by network BW or CPU performance (at
this BW level). Something else is causing the degradation to 50% of
available network BW. Do you have any ideas?
I
use filebench, it has a cifs plugin I think
Or iozone, or any other benchmarking utility, which, behind the scenes, will
write to disk and measure the throughput of each one, exactly like dd does,
except the benchmarking tools will repeat and change parameters such as
block size and filesize on
After looking around, it appears it is an inherent limitation of the
SMB protocol. It doesn't pipeline requests which means it experiences
the full 6 msecs latency introduced by MOCA. SMB2 should fix this when
it is available in CIFS.
In my test, just now (using 1Gb interconnect) I got the
My perfomance for my home file server is similar, with actual file transfers,
from the windows pc to the opensolaris (snv125) server via CIFS I get in
upload, around 100MB/s in burts of 15 seconds, average around 80MB/s (burst
probably due to zfs flushing) and read speed is 100MB/s flat line,
Setup:
Linux client (Atom 330, 1GB d...@533) connects to Solaris server (Atom 330, 2GB
d...@533)
Network connectivity through 100 Mbps MOCA link (3 msecs latency each
way)Solaris server exports the same filesystem through cifs and nfs
Operation:
dd if=/dev/zero of=test bs=16384 count=512
On Wed, Nov 18, 2009 at 4:55 PM, Yannis Schoinas yan...@schoinas.net wrote:
Setup:
Linux client (Atom 330, 1GB d...@533) connects to Solaris server (Atom 330,
2GB d...@533)
Network connectivity through 100 Mbps MOCA link (3 msecs latency each
way)Solaris server exports the same filesystem
I would expect both protocols to saturate the network. What are your
performance expectations for cifs?
CIFS performance is not limited by network BW or CPU performance (at this BW
level). Something else is causing the degradation to 50% of available network
BW. Do you have any ideas?
What's
On Wed, Nov 18, 2009 at 5:54 PM, Yannis Schoinas yan...@schoinas.net wrote:
I would expect both protocols to saturate the network. What are your
performance expectations for cifs?
CIFS performance is not limited by network BW or CPU performance (at this BW
level). Something else is causing
After looking around, it appears it is an inherent limitation of the SMB
protocol. It doesn't pipeline requests which means it experiences the full 6
msecs latency introduced by MOCA. SMB2 should fix this when it is available in
CIFS.
You can also try much larger sample sets.
Something like iometer allows you to specify queue depth to really push things
along as well.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
11 matches
Mail list logo
