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
Work is distributed randomly to HBees because the query is transferred upon invocation. This means that subsequent queries have little probability to attribute the workloads with possible cache hits (e.g on the data downloaded from S3).
A possible solution would be to let the HBees first connect to the HComb, registering the state of their cache, which would then be able to assign work according to this state.
The text was updated successfully, but these errors were encountered:
Work is distributed randomly to HBees because the query is transferred upon invocation. This means that subsequent queries have little probability to attribute the workloads with possible cache hits (e.g on the data downloaded from S3).
A possible solution would be to let the HBees first connect to the HComb, registering the state of their cache, which would then be able to assign work according to this state.
The text was updated successfully, but these errors were encountered: