RE: [PATCH v4 3/8] mem-pool: only search head block for available space
- From
Jameson Miller <jamill@microsoft.com>
- Date
- Jun 28, 2018, 14:12 UTC
- Message-ID
- <DM5PR21MB07803918120F4CC5B340230ACE4F0@DM5PR21MB0780.namprd21.prod.outlook.com>
- In-Reply-To
- <CAGZ79kbL5wjJvKj-=gtGgtMFCPs+zTwSAV-Aeo_2GNC_h=1nNA@mail.gmail.com>
> Do we have any numbers on performance or memory pressure here? > (I would think benchmarking fast-import would suffice as that is where the mem > pool originated)
I ran fast-import on the git.git and linux.git repositories - this action reports the overall memory allocated to pools. The overall memory used by pools did not change in my tests (git.git used 2 blocks, and linux.git used 12 blocks). I included this information in the corresponding commit message.
Show 7 quoted lines
> > > This pattern will benefit consumers that are able to generate a good > > estimate for how much memory will be needed, or if they are performing > > fixed sized allocations, so that once a block is exhausted it will > > never be able to fulfill a future request. > > Would this be a good candidate to contain parts of
I included these details in the commit message that adds the field indicating the cache_entry was allocated from a mem-pool.