Running ETL siss in virtual machine


Having issue with slow processing in virtual environment as opposed to physical server?

As anyone come a cross situation where running large etl packages on a virtual machine?
the Ssis packages uses SCD component.
My package is really slow in term running on virtual environment rather than physical environment.

Any one explain to me why this.

ken hanseAsked:
Who is Participating?
ken hanseAuthor Commented:
thanks John,

My ETLs runs two days in virtual environment compare to the production physical server 3hrs.

my infrastructure guy told me 8CPU in a virtual machine said good capacity on virtual server. Trust me two days to process same thing running on 3hrs in a physical environment.
JohnBusiness Consultant (Owner)Commented:
For what you want to be fast, you need to use ESX so that you have the fastest possible hardware server, have fast disks in the machine (possibly even commercial, enterprise SSD drives), and lots of memory. A virtual machine mounted in such an environment should process nearly as quickly as a real server.
JohnBusiness Consultant (Owner)Commented:
You need a fast hardware architecture as I noted to speed things up. 2 days to do 3 hours work means the hardware / virtual environment is entirely too slow.

It is not the same thing, but I can load up a Windows virtual machine on my ThinkPad and once running, it will process updates, spreadsheets and documents as fast as the host machine.
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Vitor MontalvãoMSSQL Senior EngineerCommented:
my infrastructure guy told me 8CPU in a virtual machine said good capacity on virtual server
I don't agree totally with that. Don't forget that they are vCPU and not CPU and are shared with other virtual machines. I would reduce it to half (4 vCPU) and increase the memory. SSIS packages can consume a lot of memory.
David Johnson, CD, MVPOwnerCommented:
you really have to compare apples to apples here. The biggest item you have to consider is where are the bottlenecks.. disk i/o is the normal #1 problem. #2 is RAM is there enough free ram available and lastly cpu performance.  For instance I split a sql database file locations from the default system drive where sql competed with everything else for iops and put the database / log / and temp files each on a separate spindle (physical drive) and took a 3 hour operation down to 5 minutes. Personally I'm heavily invested in Storage Spaces and its storage tiering which puts the most used data onto SSD's either automatically based on demand or manual placing the data on SSD's
ken hanseAuthor Commented:
really good feed back
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.

All Courses

From novice to tech pro — start learning today.