FTP uploads slower to shared NetApp drive device than to the physical server

Transfers to VM to NetApp \\servername\share slower than transfers to the \\physicalserver\share.  About 50% slower.
My storage hosting company describing this as current CIFS shares use backend SATA disk, while the VMDK datastores use the higher speed SAS disks.  Also you add in the overhead of CIFS protocol and the fact it has to still be copied to the VM (memory), then to the NetApp share.  This adds some latency.
I just don't see how is it related to CIFS shares or disks could be so much different.   Any advice?
LVL 17
Tiras25Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DavidPresidentCommented:
Well, several things come into play.  About the least interesting is the physical disk interface, unless you have a 1-disk volume with nothing else going on both hosts, and nothing else on the network.

Bottom line, you are sharing resources.  THe VM has overhead, anything else running on any of the other hosts have overhead.  What is going on inside the NetApp has overhead.  The protocols have overhead.  

This is the nature of the beast.  If you want better FTP performance, then probably the best way to solve the issue is get a more efficient mechanism for moving files.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It is true the SATA disks on NetApp filers are slowet than SAS or FC disks. We had deployed CIFS shares on shelves of SATA disks on 3020 heads for use with roaming profiles in an organisation with approx 2,000 users, morning logins caused chaos, and 20 to 30 minute logins, SATA disks could not provide thebthroughput required, also issues with writing profiles.

We migrated all profiles to SAS volume on the same filer, no issues with profiles.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Tiras25Author Commented:
Sorry for the delay.  Still looking into the solution to understand.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.