Jump to content
Texasguy

Vectorworks is REALLY SLOW lately!

Recommended Posts

@Zeno are suggesting we should downgrade to VW2015 because it is a more stable version of VW?

Share this post


Link to post
2 hours ago, Amorphous said:

@Zeno are suggesting we should downgrade to VW2015 because it is a more stable version of VW?

No

follow the 2015 instruction of the link to completely unistall vectorworks 2019. Then reinstall and try. Sometimes it worked for me

  • Like 1

Share this post


Link to post
11 minutes ago, Amorphous said:

Okay will give that a try. Thanks. 

 

Cancell all elements> empty trash > reboot> install last version

 

Share this post


Link to post
3 hours ago, Amorphous said:

Everything is slow! Simple things like:

 

Editing a dimension is slow.

Moving objects around is slow.

Navigating between sheets is slow

Save and commit is slow (yes it has improved, but lets face it, still slow)

 

There's a 2-3 second delay in everything I do....

 

Is anyone at Vectorworks doing anything about this??? I don't want to be frustrated anymore. 

 

Normal drawing activities, like moving or dimensioning, shouldn’t have a delay. Have you tried testing in a new document? That would determine if something is amiss or inefficient about your file. 

 

If you have a lot of verticies or end points, particularly with imported geometry, that can slow things down when you are snapping. Adjusting snap and or layer options can help, as otherwise you are asking Vectorworks to provide hundreds of SmartCursor cues in a short time. 

 

2019 added caching of sheet layer viewports. You may notice a slight delay when first navigating to a sheet layer, but then navigating within that layer should be significantly faster. If you are noticing long delays, submitting your file as a bug will help Vectorworks improve this feature. 

  • Like 1

Share this post


Link to post

I have been doing some drawing recently where I have only been using my personal symbols. No Spotlight instruments, (no focus points YAY!!!)  no Bracworks truss, no anything requiring a plug-in object with the exception of perhaps the screen tool. VW seems to move along just fine even with pretty complex drawings. As soon as I start replacing my fixtures with Spotlight instruments things start to slow down significantly. It’s also where I start getting frustrated with buggy behavior. 

 

Many VW users have transitioned from those that draw to now using VW as a plug and play solution. There is nothing wrong with that and the functionality is great, but that, along with an arguably dated architecture (CPU, GPU usage) are where the issues lie I suspect. 

  • Like 2

Share this post


Link to post

I am working on a project where I used all my own symbols to create the presentations. It is a fairly large arena show and I have been flying around it with very little difficulty. I’ve now replaced my symbols with Spotlight lighting fixtures and Braceworks truss as I am sharing this with collaborators. It has immediately become an intolerable sloth. Waiting 60 sec to change views, seeing lighting fixtures completely disappear (even “refresh instruments” won’t bring them back), and beach balls for days. I spent about 25 - 30 min just rotating six viewports. It’s amazing how much better VW works when it doesn’t have to plow through countless unseen processes   

  • Like 1

Share this post


Link to post
9 hours ago, scottmoore said:

I am working on a project where I used all my own symbols to create the presentations. It is a fairly large arena show and I have been flying around it with very little difficulty. I’ve now replaced my symbols with Spotlight lighting fixtures and Braceworks truss as I am sharing this with collaborators. It has immediately become an intolerable sloth. Waiting 60 sec to change views, seeing lighting fixtures completely disappear (even “refresh instruments” won’t bring them back), and beach balls for days. I spent about 25 - 30 min just rotating six viewports. It’s amazing how much better VW works when it doesn’t have to plow through countless unseen processes   

 

I would agree that slowness is definitely not caused by geometry alone. Native geometry is also way better than imported geometry.

Kevin

Share this post


Link to post

Are these instances of slowness witnessed on both Macs and Windows PCs?  I'm on a Macbook Pro 2016 and have really been acknowledging the bang-for-the-buck price points that are out there for the Windows OS machines.  What kind of hardware are you guys running?

Share this post


Link to post

I am on Mac. 2014 MBP, 2018 MBP and a MacPro tower. I did just realize yesterday that I apparently have lost 8mb of RAM due to a failure so more is on the way. 

  • Like 1

Share this post


Link to post
Posted (edited)
19 minutes ago, scottmoore said:

I am on Mac. 2014 MBP, 2018 MBP and a MacPro tower. I did just realize yesterday that I apparently have lost 8mb of RAM due to a failure so more is on the way. 

Thinking of investing in a Windows gaming machine (laptop for mobility) (as much as I really don't wish i had to) and to get VW on there to see if it's a MacOS vs Windows issue - I know Sketchup runs sigificantly smoother on PC's than it does on Macs (at least in my experience) so it might/can be the same for VW?... can only try to find out.

Edited by Janvin Lowe

Share this post


Link to post

@Janvin Lowe

 

We are running a PC-based WV office. Unfortunately, we face  speed issues as well. Our machines are mostly  i7700K @ 4.2GHz with Quadros and 1050Ti's. While some Mac-based users have reported some weird issues with Mojave, I don't think you'd see any significant performance increase in shifting to PCs. Currently hardware is not really what is making VW slow. IMHO it is pointless to invest large sums into hardware if that is making only a marginal difference.

 

We have very slow performance with any elevation viewports, even hidden line viewports stripped of everything extra. 2019 is faster than 2018, clearly, but multi-threading somehow seems not be quite there yet: I see CPU utilization from 12.5-25% most of the time, although curiously, with the slow viewports it seems to be multi-threading more intensely, at 84%.

 

I have an old 2012 Dell T3600 with a Xeon E5 1620 @ 3.5GHz at home; I started wondering why it seems to run 2019 practically at the same swiftness or slowness as the newer machines at the office. One reason could be the single-core performance speed, which hasn't increased so much. The number of cores have, instead.

 

If you look at this benchmark chart, you can see that a high-end i9900 is only about 1.5 times faster than an old Pentium Gold, if comparing single-core performance:

 

https://www.cpubenchmark.net/singleThread.html

 

So it would seem that complete multi-threading combined with streamlining the code would be the answer. Maybe the tech people at VW can chime in with better knowledge on this. I'm seeing only about 25% CPU usage while doing everyday work. Maybe there is more to this than that though, but it would seem the program is not using that many cores, most of the time.

 

 

 

  • Like 2

Share this post


Link to post
14 hours ago, JMR said:

@Janvin Lowe

 

We are running a PC-based WV office. Unfortunately, we face  speed issues as well. Our machines are mostly  i7700K @ 4.2GHz with Quadros and 1050Ti's. While some Mac-based users have reported some weird issues with Mojave, I don't think you'd see any significant performance increase in shifting to PCs. Currently hardware is not really what is making VW slow. IMHO it is pointless to invest large sums into hardware if that is making only a marginal difference.

 

We have very slow performance with any elevation viewports, even hidden line viewports stripped of everything extra. 2019 is faster than 2018, clearly, but multi-threading somehow seems not be quite there yet: I see CPU utilization from 12.5-25% most of the time, although curiously, with the slow viewports it seems to be multi-threading more intensely, at 84%.

 

I have an old 2012 Dell T3600 with a Xeon E5 1620 @ 3.5GHz at home; I started wondering why it seems to run 2019 practically at the same swiftness or slowness as the newer machines at the office. One reason could be the single-core performance speed, which hasn't increased so much. The number of cores have, instead.

 

If you look at this benchmark chart, you can see that a high-end i9900 is only about 1.5 times faster than an old Pentium Gold, if comparing single-core performance:

 

https://www.cpubenchmark.net/singleThread.html

 

So it would seem that complete multi-threading combined with streamlining the code would be the answer. Maybe the tech people at VW can chime in with better knowledge on this. I'm seeing only about 25% CPU usage while doing everyday work. Maybe there is more to this than that though, but it would seem the program is not using that many cores, most of the time.

 

 

 

Thanks for the insight - sure sounds like a mult-thread optimization issue - haven't looked too far into that but I'm sure they've got some verbiage about it, albeit probably just for the buzz though.  As for Windows, I'm half torn on the performance of VW and the other half on my 2016 i7 MacBook Pro which wasn't cheap but at the price and at the time I got it for, could've netted me a PC book with a signficant spec-bump.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×