Skip to content

optimize knowledge serialization #1168

@ivg

Description

@ivg

To store the knowledge base we first translate it to a bigstring and then dump this bigstring into a file. Given that knowledge base could be tremendous in size it is not only suboptimal (we create an in-memory buffer and copy the knowledge twice) but also infeasible since we may just run out-of-memory. A better solution would be to memory map the file and write knowledge directly to it.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions