Actions
Bug #10444
open
[Performance][Workbench] While in a resource #show page, switching between tabs results in fetching the object again from API server. This can cause unacceptable amount of latency for large objects such as large pipeline instances and also to collections.
Story points:
-
Release:
Release relationship:
Auto
Description
The current caching model is not helping here. In workbench arvados_base, we use the following for cache_key.
Here the "Thread.current.object_id" changes for each request making the cache basically useless in this context.
Suggest using the current user token instead.
cache_key = "request_#{Thread.current.object_id}_#{self.to_s}_#{uuid}"
Updated by Radhika Chippada
Updated by Tom Morris over 6 years ago
- Target version set to Arvados Future Sprints
Updated by Ward Vandewege almost 3 years ago
- Target version deleted (
Arvados Future Sprints)
Updated by
Actions