Skip to content
This repository has been archived by the owner on Oct 9, 2024. It is now read-only.

performance: malloc on insert #8

Open
roblatham00 opened this issue Sep 22, 2016 · 1 comment
Open

performance: malloc on insert #8

roblatham00 opened this issue Sep 22, 2016 · 1 comment

Comments

@roblatham00
Copy link

the mercury folks learned this the hard way: malloc on every operation increases latency. We talked about this for a while in the group meeting.

@halimamer
Copy link
Contributor

Efficient alloc/free of queue and list elements is in our to-do list. We will proceed in two steps:

  1. Implement a scalable allocator for internal allocations
  2. Extend the API to offload memory management to Izem.

Currently lists and queues require potentially double alloc/free operations: one set by the user who might allocate the data and pass the pointer to Izem; and another set for the internal list/queue element.

  1. will ensure fast internal memory management (goals: lock-free and cache-friendly). 2) Will avoid double alloc/free operations, and the single alloc/free set of operations will be expected to be well implemented.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants