Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

CLR sp running very slow on 64-bit virtual server... Expand / Collapse
Author
Message
Posted Friday, July 9, 2010 2:15 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 16, 2014 6:28 AM
Points: 18, Visits: 87
Hi everyone,

I have a problem with a CLR sp on SQL Server 2005.

It is installed on two different systems, one with a 32-bit server (physical) and the other one is installed on a 64-bit virtual server (VMware)...

On the physical 32-bit server the sp works ok, it takes 6,5 min to work its way through approx 77000 rows...
On the virtual 64-bit server the sp takes about 4 hours to work its way through approx 55000 rows...

Sometimes it just stopes on the virtual server... If we run smaller batches like 11000 rows it takes about 6 min...
I think it could be a memory problem but I am not sure.

Any ideas???

Br
Nicklas
Post #949776
Posted Tuesday, August 17, 2010 7:16 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Tuesday, September 2, 2014 1:10 PM
Points: 1,708, Visits: 1,793
Without further details about how your VM is configured, its impossible to offer anything intelligent to look at. What is the difference in configuration CPU/Memory/DiskIO between the physical server and the VM? Does the VM have dedicated resources on the host to it, or is the host oversubscribed and coscheduling? What is the host virtualization platform (it makes a difference because the counters for the guests at the host level differ from platform to platform). Since this is a 64 bit VM did you set max server memory, enable lock pages in memory? What is the values for SELECT @@VERSION from both machines?

Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs
Post #970394
Posted Wednesday, August 18, 2010 1:45 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 16, 2014 6:28 AM
Points: 18, Visits: 87
Sorry but I don't know the configuration to well... it is another company that takes care of that.

I don't think that the virtual server has dedicated resources. I have read that if there is a lot of transactions (inserts and updates) the virtual environment often is slower.

We have made some changes, we have disabled some triggers and made some other changes as well. It is now working very good.

Thanks for your answer.

/Nicklas
Post #970960
Posted Wednesday, August 18, 2010 4:58 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Tuesday, September 2, 2014 1:10 PM
Points: 1,708, Visits: 1,793
mitega (8/18/2010)
Sorry but I don't know the configuration to well... it is another company that takes care of that.

I don't think that the virtual server has dedicated resources.


This would be the first suspect for problems. If you don't know the configuration of the virtual environment then you don't know that you have sufficient resources allocated to make any kind of comparison between the 32 bit physical server and the 64 bit virtual server.


I have read that if there is a lot of transactions (inserts and updates) the virtual environment often is slower.


This is a myth, plain and simple. I have been running high transaction databases in SQL Server virtualized for nearly 4 years now, and if the virtual environment is configured correctly, and has similar resource allocations to what a comparable physical environment would have, there is little to no difference in performance characteristics. Virtualization gets a bad wrap when to many guests are run on a physical host, resulting in oversubscription of the resources, or when insufficient resources for example Disk IO have been allocated when compared to what would have been done in a physical implementation.


Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs
Post #971521
Posted Thursday, August 19, 2010 1:15 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 16, 2014 6:28 AM
Points: 18, Visits: 87
Ok... I just think that it should perform better since it is a new environment with some "big" servers which I hope they have configured correctly... maybe they have to many guests on their hosts. They have moved all the physical servers to the virtual environment.

The system has performed slower since the switch from physical servers to virtual servers but I am no expert on virtual machines...
I just thought it was strange that a small and a few year old physical server should perform better than this new environment. But if it is as you say that it is only a myth then I will stop reading the articles that I have read.

I will suggest that they increase the environment with one or two more hosts. Maybe the servers will get more resources to work with.

Thanks for your response!
Post #971649
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse