Skip to content

Re-use HBee cache #8

Open
Open
@rdettai

Description

@rdettai

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions