All of lore.kernel.org
 help / color / mirror / Atom feed
From: L A Walsh <cifs-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>
To: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: kudos & congrats on efficiency.
Date: Fri, 26 May 2017 11:12:36 -0700	[thread overview]
Message-ID: <59287014.4040006@tlinx.org> (raw)

I tend to be a bit of a performance-geek -- often running various 
self-relevant benchmarks to see how long things take and working on 
optimizing configs for  speed & efficiency. 

I wanted to backup a 45.5GB dir (with 260 subdirs, & 633 files) from my
Win7SP1 PC to my home server.  I frequently have the Win7 disk
(SSD-based) mounted on a top-level dir. 

An aside, I want to repeat a kudo relating to win-symlinks appearing
as linux-native symlinks via CIFS.  That's excellent.  It may have
just 'fallen out' from other work, but it's still very cool.

Second is on efficiency, uncovered by running tar.  I thought
the 45G would take a few-several minutes to xfer even with my 8Gb (says
10, but get a 20% penalty for having an older PCIe bus) ethernet.
It took < 2 minutes to write to a tar file.  I ran the tar again
(after dropping local caches) w/output to /dev/null...
took 82.02s : average 568MB/s!  With CIFS taking 70-80% cpu.
A rerun on the server after another dropcache, averaged 687MB/s. 
Maybe subsequent runs benefit from the win7-cache.
Not sure how to readily drop the Win7 cache (other than alloc'ing
all mem in the machine and forcing the cache to be dumped)...

Anyway, for comparison, my current version of samba
gives ~450MB/s for reads and ~200MB/s for writes.

Congrats!
-Linda W.

                 reply	other threads:[~2017-05-26 18:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=59287014.4040006@tlinx.org \
    --to=cifs-gt3auasyrbtytjvyw6ydsg@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.