Improve Performance for Large Projects
complete
Chufan Huang
The Application is still pretty slow in 2024...
Patricia (ProtoPie Team)
complete
This issue has been addressed in version 7.6.0, released on March 22, 2023:
If you still experience performance issues when working on large prototypes, please contact our support team at https://www.protopie.io/form/contact-us
Nazario Fraija Pulido
Working on a project with many imported layers from figma. I'm creating motion prototypes of our web application.
It's a DesktopHD 1440p scene with mainly lots of shapes and components with shadows overlayed, a lot of text and some masks, no bitmaps.
Running on a Late 2019MBP with 32GB of Ram.
Where my computer struggles is zooming, I literally need to wait seconds to see a zoom step, it's really strange because panning and selecting works fine.
I've tried reducing nesting and visible layers to the minimum but even with all layers invisible zooming is just as bad.
In other projects/scenes with less shapes/vectors/components around zooming is much more performant.
I zoom using the trackpad or mouse scroll.
Any hints at improving zooming some time soon?
Harald Skogland
just latching on to this one:
+1 one for the experience of huge slow-down.
Does anyone know what current bottlenecks are? Will it help to:
* reduce vectors?
* reduce layer groups/containers?
and,
* is number of triggers and responses a factor?
Hoping ProtoPie will improve performance! thanks,
Harald Skogland
So just logging on the next day, and performance is greatly increased.. Is it possible that somehow the way cache or scratch files becomes bloated and unmanageable after very long work sessions? I'm in the same Pie project as the day before, but now things are running fairly smooth, altough with occasional slow-downs. Yesterday, in the same file, while duplicating, deleting or any single, and particularly bulk action, ProtoPie would need 3-10 seconds to process each request.
Patricia (ProtoPie Team)
Merged in a post:
Library layer/canvas interaction performance
Martin Boerma
We are building out a team library. Even with limited components added to the library canvas and layer interaction is degrading. In other words selecting layers has a latency. The time between the mouse click and the actual selection on the canvas. The latency is substantial. As in, it gets in the way.
This is typical for tools that manage a lot of vector points. But it's also one of the main points of irritation among designers when things become sluggish.
I reported this already with protopie support and as usual they pick it up real quick. But I want to mention it here as well. Because performance issues should be tackled before they get out of hand.
Cheers,
Martin
Patricia (ProtoPie Team)
Merged in a post:
Improve nested components performance
S
Sorin Oprisor
let's say we have a component that is nested inside another component that is nested inside another ... let's say 3-4 levels down
editing that component is very slow
operations like moving layers become very time consuming (10-15 seconds for moving a layer)
would be great if this can be optimized a bit
E
Edgar Kay
Curious what machine you're working on (RAM, CPU...).. about to start a huge project and this sounds alarming :)
Sammy Guergachi
Edgar Kay: 32GB Ram, i7 CPU, SSD, and 1070 GTX. So its not specs I dont think. I am trying to work off of a Adobe XD doc which itself is a large project that I wanted to try improving with protopie, but importing it into prototpie proved impossible (infinite load time), and when I tried importing a single art board with many components with many layers it just got super slow.
E
Edgar Kay
Sammy Guergachi: I sometimes end up receiving errors when importing heavy boards from sketch. Some layers will get lost, some misplaced…
and suk
Sammy Guergachi: I agree it does get slow sometimes on my old computer, I would also try higher specs like 2080 -3080 (GTX-RTX) unfortunately 1070 is starting be to dated.
Sammy Guergachi
and suk: thats ridiculous. 1070 should actually be overkill for this application. Theres clearly a lack of optimization in code if its slow, its not my specs.
J
Jeff Clarke
I’m also noticing a severe degradation in performance. It’s the worst when reordering layers, which can often take 15-30 seconds to update. But in general, performance in the editor is definitely sluggish.