Skip to content

Allows option of storing best candidate powerset in the rocksdb #600

@pranavbhole

Description

@pranavbhole

Currently we are storing best candidates powerset in memory, we should consider storing in this the optional rocksdb. In the case of number of columns goes up above 100, powerset generates many entries and occupies the heap space. For lesser number of cols, in memory store is good.

Any thoughts? @patelh @pavanab4u

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions