Caching of experimental factors
|Reported by:||Jari Häkkinen||Owned by:||Nicklas Nordborg|
The experiment properties view takes a long time to appear when there are many experimental factors associated with the experiment. This is due to the costly check of all inherited annotaions. If the experimental factors are cached with each experiment the performance and user experience would be improved.
I suggest that we add a caching mechanism for experimental factors and the user has to actively update the experimental factors when needed.
In the experiment properites tab experimental factors listing should show a caching status (i.e., when the cache was last refreshed), allow the user to update a single annotation or all annotations at once.
Could such a caching also improve the performance experiment explorer? Using the experiment explorer is very slow and it might be a consequence of expensive annotation queries.
Change History (20)
comment:1 by , 14 years ago
|Priority:||major → critical|
|Status:||new → assigned|