I’m reading a load of stuff from a database - and 20% of my time is spent waiting for, and freeing memory allocations for String. Any wizzy thoughts?
I’m working on the other 80% right now ![]()
I’m reading a load of stuff from a database - and 20% of my time is spent waiting for, and freeing memory allocations for String. Any wizzy thoughts?
I’m working on the other 80% right now ![]()
Custom allocator? The JUCE-Team could implement a custom allocator wich is reusing already reserved memory.
It looks most of the time is used for the fixed length memory reservation new (and not new[]) , which is relatively easily optimizable using a memory pool.
Oh I see - I hadn’t looked at that properly…