3 ms·
Unstable, very crash prone with just a few users designing 10 plus pages. And a huge memory hog too. I run it on Dedicated server with 64GB Ram , it starts to
by v3ss0n 11mo ago
Unstable, very crash prone with just a few users designing 10 plus pages. And a huge memory hog too.
I run it on Dedicated server with 64GB Ram , it starts to lag as soon as a 5-6 pages and memory 20GB, lagging out the whole team and then crashes.
- shakna 11mo agoFigma is a huge memory hog, too...
- mitemte 11mo agoFigma has become absolutely shocking in the past few years. The performance is so bad these days. It doesn’t help that almost every designer doesn’t care to split things into more than one document. I’ve seen Figma documents with hundreds of screens.
- okhobb 11mo agoI'm sure if the original developer bothered to show up again he could fix it in a weekend.
- gyomu 11mo ago> It doesn’t help that almost every designer doesn’t care to split things into more than one document That’s how these tools encourage you to use them. If the tool crumbles under its own usage modalities, that’s because it’s poorly designed, not the user’s fault.
- 542458 11mo agoYou don't need to split into multiple files to make large documents manageable, multiple pages works just fine (pages you're not using aren't loaded). But even still, I have absolutely massive pages with ~100 screens on them that work just fine on this base-tier M2 MBA. Honestly given the complexity of the screens involved I feel Figma's performance is pretty reasonable. (Now, library publish and update - that's still unreasonably slow IMO)
- v3ss0n 11mo agoFigma can handle unlimited amount of screens in one huge canvas
- SoKamil 11mo ago> very crash prone > And a huge memory hog On the server side or the frontend side?
- v3ss0n 11mo agoWhat we tested is both. It start to choke on Browser and then server side.