|
|
|
|
|
by naiveter
13 days ago
|
|
Is the high expense coming from cache misses? If their workload does need to wait for a long time before it can continue, I wonder would starting new sessions and having to re-read the contexts and results anyway be any cheaper. |
|
Yup. They can't keep your workload in cache forever, or they would run out of cache for users.
> I wonder would starting new sessions and having to re-read the contexts and results anyway be any cheaper.
Yes, that's what they recommend