"Set variables" with performance impact

Anybody experienced a significant performance issue when using ‘set variable’ function?

I am using it to change the what variant of a component is visible. For example let’s say I have a side menu with 2 menu items on the left and a content instance on the right. When clicking each side menu items, they change a variable called ‘content ID’ to be ‘Page 1’ or ‘Page 2’ respectively. The content instance come from a component with 2 variants, and the property value of the variant is attached to the variable ‘content ID.’

So clicking the menus change variable value (string) and the content instance shows corresponding variant. Yes, working. But it takes a few seconds… which is not really OK. I think it was working smoothly beforehand but at a certain point (highly likely after an update) this started lagging.

Anyhow who has similar experience or knows a solution/work-around?

5 Likes

Came looking to see if anyone else was experiencing this - My complex prototype has become unusable now that every Set Variable interaction takes a few seconds.

1 Like

I am experiencing a lag with components that set variables as well. Other interactions don’t have any lag.

Hey all - I wanted to jump in to comment on the performance issues. It definitely could be some kind of issue on our end, but it could also be something expected if your design system has a lot of complex components, variables, etc.

These kinds of issues are really hard to diagnose on their own without any additional context (it’s most helpful if we can look at your design file, have you provide a screen recording of behavior, write out step by step directions, etc.). I do want to acknowledge that’s not possible in all situations because of NDAs

I understand that may come off negatively, but my honest suggestion is to file a support ticket reporting these issues.

It makes sure that you get individualized solutions, and allows support to review your files in a secure way.

If this is possible for any of you, and you’d like to move forward, please do the following:

  • Fill out the form linked here

  • Share edit access to files you’re having issues on with support-share@figma.com. You won’t be charged for this seat, as this is our official support review account. If you can’t share, that’s okay. Please still file a ticket.

  • If you can share your files, please indicate In the body of the ticket you file that you’ve shared edit access to it, and provide the exact name of the file.

  • From there, someone will reply and get back to you with suggestions. Please note: there may be some instances where they’ll need you to verify some info for security purposes.