Deployment Solution

Hello everyone,

I've been experiencing some deep slowness on my console lately.

This is actually happening on two of my consoles.

Everytime I click on a job, expend a folder, close a window... it looks like freezing for 5-10seconds or more.

This is extremely annoying and despite I change the amount of memory, it doesn't help.

I have this working on a Windows 2008R2 + SQL 2012

We have it in each country I support, and working perfectly in 4 but not in two.

Any idea ?

Thank you.

Virtual machines?  How many clients are connected to the 2 not working?  What else is running on those servers?  Shared proc's?  Does the console "start" fast after a reboot and then slow down?  What does Task Manager say at the time you see this?  Does it matter if you run the console locally vs running it on a remote workstation?

Hi Thomas,

Thanks for your questions.

Here some answers:

We are runing the console directly on the server which is only used for this purpose (DS).

Restarting doesn't help much and it looks freezing when I'm going over the jobs, just like if it was SQL loading all the history for the database.

Looking at the TaskManager, SQL is taking 50% of the CPU ressources (we have two).

I have no idea on how to optimize SQL so far.

Hope this helps.
Franck

If you run the console remotely, see if it makes a diff.  If there are any other apps on the box, move them to a different system (stop using them) and see if that helps.  How many clients?  If you're doing a LOT with DS (e.g. delivering apps as well as imaging) that may cause issues.  Check network performance as well - maybe a NIC is bad and forcing it to half duplex might help for example?

And do a REAL comparison of those 2 with the others.  Different hardware?  Diff versions of SQL?  Different client counts?  Different ...  you get the picture.  If there is no "real" difference, you're left with either some sort of damage on a code level (e.g. virus/corruption) or damage to hardware (e.g. NIC/proc/overheating/whatever).

Just a thought or 2...

NOt sure about relevance against SQL 2012, but we restrict the RAM usage in SQL to 1 GB, which is not set per default (referring to 2k8 here). Also, the console refresh and maintained history could have impact. If you clean out history older than xx days may help speeding up things...