axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Created: (AXISCPP-181) Entry/exit trace performance bad with trace off
Date Fri, 01 Oct 2004 10:04:31 GMT

  A new issue has been created in JIRA.

View the issue:

Here is an overview of the issue:
        Key: AXISCPP-181
    Summary: Entry/exit trace performance bad with trace off
       Type: Bug

     Status: Open
   Priority: Major

    Project: Axis-C++
             Basic Architecture

   Assignee: Mark Whitlock
   Reporter: Mark Whitlock

    Created: Fri, 1 Oct 2004 3:03 AM
    Updated: Fri, 1 Oct 2004 3:03 AM

When Axis C++ is built with trace entry/exit and run with trace off,
performance is impacted because the trace tool generates...
if (g_pAT) {
    ... Do trace stuff ...
g_pAT is null before trace is initialised, but is not null when trace 
is initialised but off. So the the string manipulation and invoking
the trace class happens before we realise trace is actually off. This
works, except that it hits performance. The trace tool should generate
if (g_pAT && g_AT->traceOn())
or something similar.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message