I am being a little bit more precious on the background to make the issue more feasible to you:
The Graph Visualizer is based on 2 filters in our app that can both be set in two separate filter elements. In the usual case, the user would set both variables and then expects the Graph Visualizer to compile. This would work fast as the Graph Visualizer would only need to plot one smaller Graph.
The issue is now that the Graph Visualizer already starts compiling after the first filter is set. As there may be > 25 different combinations, if the second filter is not yet set, the Graph Visualizer compiles > 25 graphs and hence, is quite slow.
A solution would be to have e.g. 2 filters that can be set, then have an execution button (or something the like, e.g. trigger button) that assigns the values to the variables and as a consequence have the Graph Visualizer react to the set filters.
Abstractly speaking, filters are not set right in the moment when they are selected but later once another button is pressed (Thinking of e.g. if you book a flight, you are first inputting all your data like Abflughafen, Ankunft, Zeit, etc. and the have a button to start the search).