Visio 2013 VERY slow

Like many of you, I arrived here via a web search for the solution to an app that runs so slow it is unusable.  I have tried all the recommendations offered by the good folk here and experienced zero detectable improvement. Given the number of years this problem has been known yet not addressed, my expectation is Microsoft will never fix it and will just roll on to the next version of Office.  Meanwhile, I've rolled back to Visio 2010 and don't anticipate changing away from it any time soon.  Very disappointing response Microsoft.

Thanks for your suggestion It worked but still as you said its not up to par .....

Hi Rich,

I concur with you completely. We still find Visio 2013 to be borderline unusable due to the slowness in doing certain tasks. Our add-on software has been crippled by the changes and we are facing yet another rewrite to make our application functional.

This is so bad that we recommend to our clients that if they have Visio 2010 licenses available to stick with 2010 and stay away from 2013. As for ourselves, we are exploring alternatives to Visio and will most likely move to dump it.

I too don't have any expectation to see this issue fixed.

Just my two cents.

Carl

I just wanted to state that this problem does not appear to be isolated to the shapes window, or the pan and zoom function. 

I have written vba for a high resolution timer, to measure the performance of a sub routine I am having issue with. I noticed that using dropmany in visio 2010 results in sub-second execution time; however using dropMany in Visio 2013 can take anywhere from 6.5 seconds to 22 seconds... depending on the number of shapes dropped. 

I should note that I performed the exact same test, and executed the exact same sub-routing, in both versions... and can say with absolute certainty that dropMany seems to have been very poorly written for Visio 2013. I've also had a total of 8 co-workers also test this, 4 of them use Visio 2010, and another 4 use Visio 2013... and their results are identical to my own. So this also means that it is not an issue isolated to my computer, and that it is definitely a difference in the way that Visio 2010 and 2013 handle the dropMany function.

I will submit this as a bug... but I have absolutely no hope that Microsoft will fix this in a timely manner. I read all 5 pages of this thread, and it seems it took Microsoft nearly 2 years to fix the original problem mentioned. Visio is such an expensive product, and yet Microsoft seems to offer very poor support for it.

We investigated these issues and have released some improvements in the Jun Visio patch (fixes are around panning and zooming). The patch is present here - http://support.microsoft.com/kb/2878322/en-us