You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2011/05/16 02:37:47 UTC

[jira] [Created] (TS-784) Don't use class allocator for remap processing when no remap threads are enabled

Don't use class allocator for remap processing when no remap threads are enabled
--------------------------------------------------------------------------------

                 Key: TS-784
                 URL: https://issues.apache.org/jira/browse/TS-784
             Project: Traffic Server
          Issue Type: Improvement
            Reporter: Leif Hedstrom
            Assignee: Leif Hedstrom
             Fix For: 2.1.9


We're currently using the class allocator for allocating RemapPlugins instances, even when no remap processing threads are enabled. This is a bit wasteful, since we can just allocate this (quickly) on the current thread stack.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (TS-784) Don't use class allocator for remap processing when no remap threads are enabled

Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom resolved TS-784.
------------------------------

    Resolution: Fixed

> Don't use class allocator for remap processing when no remap threads are enabled
> --------------------------------------------------------------------------------
>
>                 Key: TS-784
>                 URL: https://issues.apache.org/jira/browse/TS-784
>             Project: Traffic Server
>          Issue Type: Improvement
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 2.1.9
>
>
> We're currently using the class allocator for allocating RemapPlugins instances, even when no remap processing threads are enabled. This is a bit wasteful, since we can just allocate this (quickly) on the current thread stack.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira