[Ace-users] [ace-users] [usage question] ACE_Log_Msg / ACE_Log_Record - no allocator

[Douglas C. Schmidt]

Hi Bogan,

>I am new to ACE and found no way to specify the allocator for 
>ACE_Log_Record internal buffer.

To ensure that we have proper version/platform/compiler
information, please make sure you fill out the appropriate problem
report form (PRF), which is in

$ACE_ROOT/PROBLEM-REPORT-FORM
$TAO_ROOT/PROBLEM-REPORT-FORM

or in

$ACE_ROOT/BUG-REPORT-FORM
$TAO_ROOT/BUG-REPORT-FORM

in older versions of ACE+TAO.  Make sure to include this information
when asking any questions about ACE+TAO since otherwise we have to
"guess" what version/platform/compiler/options you've using, which is
very error-prone and slows down our responsiveness.  If you don't use
the PRF, therefore, it is less likely that someone from the core
ACE+TAO developer team will be able to answer your question.
Naturally, we encourage and appreciate other members of the ACE+TAO
user community who can respond to questions that they have the answers
to.

>On my understanding each time you log something using ACE_Log_Msg 
>another ACE_Log_Record is created which in turn creates its underlying 
>data (4 KB) on the heap. This can happen very often and may have a 
>negative impact on the overall performance of the application.

No, that's incorrect.  the 4 KB of data is allocated using
thread-specific storage (see the discuss in the POSA2 book at
www.cs.wustl.edu/~schmidt/POSA/POSA2/), so the 4 KB is allocated only
once for each thread.

>Is there a way to control the allocation of ACE_Log_Record data without 
>overloading the global new operator?

No, but this shouldn't be necessary, as per the discussion above.

Thanks,

Doug
-- 
Dr. Douglas C. Schmidt                       Professor and Associate Chair
Electrical Engineering and Computer Science  TEL: (615) 343-8197
Vanderbilt University                        WEB: www.dre.vanderbilt.edu/~schmidt
Nashville, TN 37203                          NET: d.schmidt at vanderbilt.edu