Plasmic is extremely sluggish–interactions all cause loading spinner

Issues
1

Plasmic is extremely sluggish for me, unable to interact with the tool itself and more than a minute to full load the project. Any interaction causes a loading spinner

2

Are you still having issues ?

3

Yeah I’m still having this issue

4

Another dev on our team is running into sluggish initial loads

5

@responsible_spider, I feel your pain. As our project size increased, the Studio’s performance decreased. Here are my best tips:

  1. Try using Microsoft Edge, it helped prevent crashes for me, as it natively allows more memory allocation than Chrome
  2. Turn ON hardware acceleration in your browser settings
  3. Use Focus Mode in Studio to the extent that you can.
  4. Interestingly enough, force quitting Adobe’s creative cloud and other Adobe services, even though they weren’t using much memory has helped.
  5. Ensure that there isn’t any code that is on your host server that could be making the artboard sluggish.
    Hope you’re doing well, sir!
6

Could you help here @victor ?

7

I am actually noticing the worst performance coming from plasmic watch. It usually takes around a minute or two to propagate a change from the studio.

Am I alone?

8

Hey, guys! I just wanted to follow up on this topic, as I’ve found something that has DRAMATICALLY improved performance within Studio.

I’m unsure if this will help you, but it made such an impact for us, I wanted to take the time to share:

  1. We refactored ALL components to change the visibility settings from “Not Visible” to “Not Rendered” (where appropriate). It makes sense that this would have a cumulative performance impact, as we were asking all of the elements to be rendered, but not visible. “Not Rendered” is a little more buried, so perhaps many users are selecting “Not Visible” most of the time (see attached image)
  2. Remove any unnecessary instantiations of complex placeholder components. For example, a list where we override the contents with dynamic content anyway.
  3. Check to ensure that component architecture within Studio is optimized. (e.g. Make sure the components you have on every page like a navbar or footer don’t have any unnecessary components, elements.)
    I hope this helps. We’re delighted with the performance improvements after these steps.

@responsible_spider

Screen Shot 2023-01-12 at 11.47.38 AM.png
Screen Shot 2023-01-12 at 11.47.38 AM.png608×602 21.4 KB

Screen Shot 2023-01-12 at 11.48.03 AM.png

9

Thanks @parliamentary_trout! Your guide seems very well thought