Re: [Boost-users] Stupid ostringstream question

From: Richard (richard_at_[hidden])
Date: 2007-07-27 16:17:32

Well - I have zero experience here.

I remember that they were frequently advertised in the back of computer mags
a few years back.  Try Google?  I saw...

http://www.freedownloadscenter.com/Programming/C_and_C++_Tools_and_Component
s/SwiftAlloc_Memory_manager_replacement.html

and

http://www.newcodeinc.com/

Another possibility might be to look at how your app uses memory.

If you have vast numbers of objects all the same size you might benefit from
a home written replacement for operator new.  If you special case them all
into a special pool it might get them out of the way of everything else.
The general purpose manager that ships with the compiler is just that -
general!  Sounds like you have a specific problem.

HTH,

- Richard

-----Original Message-----
From: boost-users-bounces_at_[hidden]
[mailto:boost-users-bounces_at_[hidden]] On Behalf Of Bill Lear
Sent: 27 July 2007 21:01
To: boost-users_at_[hidden]
Subject: Re: [Boost-users] Stupid ostringstream question

On Friday, July 27, 2007 at 20:47:54 (+0100) Richard writes:
>Have you tried investing in a replacement memory manager?

Such as?

>It might give you a bigger overall payback than just tinkering with one
>aspect.

Certainly possible, however, it is also possible that the sheer size
and number of objects we have in our application makes it inherently
difficult for dynamically-allocated memory for small objects to work
very well at very high memory usages.  Thus the hope for a hybrid
static store and ostringstream.

Bill
_______________________________________________
Boost-users mailing list
Boost-users_at_[hidden]
http://lists.boost.org/mailman/listinfo.cgi/boost-users