Chewing_Bever/lnm

Region allocator #9

New issue

Open

opened 2024-02-08 15:39:52 +01:00 by Jef Roosens · 1 comment

Jef Roosens commented

2024-02-08 15:39:52 +01:00

Owner

Connections already reuse allocated memory where possible, but a region allocator would allow stronger control and reuse of memory, preventing a busy server from performing tons of allocations when processing lots of connections.

Connections already reuse allocated memory where possible, but a region allocator would allow stronger control and reuse of memory, preventing a busy server from performing tons of allocations when processing lots of connections.

Jef Roosens added the

label 2024-02-08 15:39:52 +01:00

Jef Roosens commented

2024-02-14 10:30:33 +01:00

Author

Owner

In this case, with a region allocator the best idea would be a fixed-size region allocator, where e.g. connection structs are reused (or perhaps a separate region per custom context if we implement that issue).

In this case, with a region allocator the best idea would be a fixed-size region allocator, where e.g. connection structs are reused (or perhaps a separate region per custom context if we implement that issue).

Sign in to join this conversation.

No labels

No milestone

No project

No assignees

1 participant

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: Chewing_Bever/lnm#9

No description provided.