Think about potential memory issues with refreshing and many gvars #20
Labels
Feedback needed
Please add a comment if you have a relevant idea or opinion
help wanted
Extra attention is needed
To store correlations,
gvars
may accumulate over time when refreshing the app or refitting. If the data / priors are particularly large, this may cause memory issues.We should try to delete caches each time a new fit is executed (and store the
initial_fit
/generate_fit result
) but delete "temporary objects". As far as I can see, starting "fresh" is intended for most of the fits.I believe, this should be relatively easy to implement with the current architecture but providing a
setter
method toFitGUI.fit
.@millernb: do you have any suggestions for how to best remove unneeded
gvars
?The text was updated successfully, but these errors were encountered: