On 2015-09-28 03:11 PM, Markus Mohrhard wrote:
I'm not sure if I understand your comment. Can you please clarify what you mean
with that? Maybe my understanding of our
memory allocators is bad but I see not how this comment applies to the
discussion.
I'm saying that in general I regard changing allocators as doing optimisation in the wrong place - if your allocator is
a real bottle-neck, you would probably be better off looking at optimising the code that __calls__ the allocator, rather
than messing with the allocator itself.
For example, if you had code that did:
vector<int> buffer;
for (int i=0; i<1000000000; i++)
buffer.push_back(i);
you'd be better off inserting a
buffer.reserve(1000000000)
just before the loop, to avoid the std::vector's resize-and-copy operation.
But that's just my opinion, feel free to experiment away if allocators are your
thing :-)
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
