You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While it should be possible to use global storage as a cache level, we currently have some hard-coded assumptions and scalability issues because SCR generally assumes cache locations are using node-local storage.
For example, when inspecting the cache on restart, one rank is responsible for distributing work. With global storage, this means rank 0 will have to talk with every process in the job, which becomes an N-to-1 bottleneck.
We should extend SCR to efficiently support global cache locations.
While it should be possible to use global storage as a cache level, we currently have some hard-coded assumptions and scalability issues because SCR generally assumes cache locations are using node-local storage.
For example, when inspecting the cache on restart, one rank is responsible for distributing work. With global storage, this means rank 0 will have to talk with every process in the job, which becomes an N-to-1 bottleneck.
We should extend SCR to efficiently support global cache locations.
Related to #133
The text was updated successfully, but these errors were encountered: