plm search init uses lot of RAM #18

Open
opened 2024-01-28 14:26:03 +00:00 by quentin · 2 comments
Owner
No description provided.

I might look into it.
Currently the search initialization is done in a pretty naive way (list all published post, from this and other instances; we could paginate instead of loading everything to memory), delete them each (which is a non-free no-op, but shouldn't consume ram) and insert them into tantivy (where there might be some tuning to do to flush more often)

I might look into it. Currently the search initialization is done in a pretty naive way (list all published post, from this and other instances; we could paginate instead of loading everything to memory), delete them each (which is a non-free no-op, but shouldn't consume ram) and insert them into tantivy (where there might be some tuning to do to flush more often)

I've created Plume!1153 upsteam

I've created [Plume!1153](https://git.joinplu.me/Plume/Plume/pulls/1153) upsteam
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/nixcfg#18
No description provided.