Layout, CPU hog
-
does anyone else find that layout is incredibly CPU hungry and Memory Hungry? i find that it eats up to 90 - 100% of my cpu sometimes and regulary is about 200-300 mb in taskamanger, im not so bothered about ram as i have 1.25gb of it. im just extremly curious why it is this intensive? i also find that it is very slow sometimes
-
LO creates high quality (and big size) png images from your model on its pages. This needs a lot of memory to keep in mind sometimes.
Also note that this is still a Beta release and I'm sure that performance is one of the issues Google is trying to improve.
-
Hi,
thanks for the reply, i was just curious thanks for shedding light on the memory issue! any ideas about cpu? that's something i defiantly think Google need to improve on, but apart from that i think it truely is a great piece of software! -
In File->Document Setup->Paper, keep rendering resolution low while editing, then increase it for final printing. It'll tax any machine to take an Arch D or E paper with large models. You can also get the CPU going when you're in edit mode on text fields or models - what's really happening is that you're firing up a SketchUp Viewer, and when you exit the model you're asking for a 2D export of that model. That's a bit of work. You can also purge unused things from time to time - File->Document Setup->References and hit the "Purge" button.
We are working on better performance. Thanks for the feedback.
Barry
-
Thanks for the reply barry, I appreciate the help, it really does help speed up layout
now i dont have to write stuff in notepad++ and copy over heheWill
-
thanks i shall test the new version!
-
@rocker9455 said:
does anyone else find that layout is incredibly CPU hungry and Memory Hungry? i find that it eats up to 90 - 100% of my cpu sometimes and regulary is about 200-300 mb in taskamanger, im not so bothered about ram as i have 1.25gb of it. im just extremly curious why it is this intensive? i also find that it is very slow sometimes
LO2 on Win has multi-core support now, so it should feel a little more responsive.
LO1 would always render every time you changed the inserted model (size/rendering props).
LO2 now has a delayed rendering option so its up to you when you want to render.
LO2 uses a lot less memory now and handles large paper sizes. -
I think the Googies have fixed the memory leak issue now so it should be better!
-
Yeh, Its so much better now, much faster!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login
Advertisement