You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2014/10/07 23:16:34 UTC

[jira] [Updated] (TS-3116) Add support for tracking the use of the ioBuffers

     [ https://issues.apache.org/jira/browse/TS-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Call updated TS-3116:
---------------------------
    Description: 
There is partial support for tracking ioBuffer usage with TRACK_BUFFER_USER and the configuration option proxy.config.res_track_memory.  The underlying data structure to store the information is missing.

This information will be reported when the user sends a SIGUSR1 signal to traffic_server or is part of the periodic memory logging reports.

Example:
{code}
                                          Location |          Size In-use
---------------------------------------------------+------------------------
                      memory/IOBuffer/FetchSM.h:62 |                 8192
                      memory/IOBuffer/FetchSM.h:64 |                65536
               memory/IOBuffer/InkIOCoreAPI.cc:491 |              3346432
                  memory/IOBuffer/PluginVC.cc:1009 |                65536
                  memory/IOBuffer/PluginVC.cc:1012 |                    0
  memory/IOBuffer/ProtocolProbeSessionAccept.cc:39 |              9900032
          memory/IOBuffer/HttpClientSession.cc:230 |              1703936
                    memory/IOBuffer/HttpSM.cc:5609 |                16384
                    memory/IOBuffer/HttpSM.cc:5722 |                    0
                    memory/IOBuffer/HttpSM.cc:5917 |                    0
                    memory/IOBuffer/HttpSM.cc:6172 |                    0
                    memory/IOBuffer/HttpSM.cc:6208 |                    0
           memory/IOBuffer/HttpServerSession.cc:87 |               516096
                  memory/IOBuffer/HttpTunnel.cc:95 |                    0
                 memory/IOBuffer/HttpTunnel.cc:100 |                    0
                     memory/IOBuffer/Cache.cc:2586 |               765952
                     memory/IOBuffer/Cache.cc:2600 |            226947072
                                             TOTAL |            243335168
{code}

  was:
The is partial support for tracking ioBuffer usage with TRACK_BUFFER_USER and the configuration option proxy.config.res_track_memory.  The underlying data structure to store the information is missing.

This information will be reported when the user sends a SIGUSR1 signal to traffic_server or is part of the periodic memory logging reports.

Example:
{code}
                                          Location |          Size In-use
---------------------------------------------------+------------------------
                      memory/IOBuffer/FetchSM.h:62 |                 8192
                      memory/IOBuffer/FetchSM.h:64 |                65536
               memory/IOBuffer/InkIOCoreAPI.cc:491 |              3346432
                  memory/IOBuffer/PluginVC.cc:1009 |                65536
                  memory/IOBuffer/PluginVC.cc:1012 |                    0
  memory/IOBuffer/ProtocolProbeSessionAccept.cc:39 |              9900032
          memory/IOBuffer/HttpClientSession.cc:230 |              1703936
                    memory/IOBuffer/HttpSM.cc:5609 |                16384
                    memory/IOBuffer/HttpSM.cc:5722 |                    0
                    memory/IOBuffer/HttpSM.cc:5917 |                    0
                    memory/IOBuffer/HttpSM.cc:6172 |                    0
                    memory/IOBuffer/HttpSM.cc:6208 |                    0
           memory/IOBuffer/HttpServerSession.cc:87 |               516096
                  memory/IOBuffer/HttpTunnel.cc:95 |                    0
                 memory/IOBuffer/HttpTunnel.cc:100 |                    0
                     memory/IOBuffer/Cache.cc:2586 |               765952
                     memory/IOBuffer/Cache.cc:2600 |            226947072
                                             TOTAL |            243335168
{code}


> Add support for tracking the use of the ioBuffers
> -------------------------------------------------
>
>                 Key: TS-3116
>                 URL: https://issues.apache.org/jira/browse/TS-3116
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Bryan Call
>            Assignee: Bryan Call
>             Fix For: 5.2.0
>
>
> There is partial support for tracking ioBuffer usage with TRACK_BUFFER_USER and the configuration option proxy.config.res_track_memory.  The underlying data structure to store the information is missing.
> This information will be reported when the user sends a SIGUSR1 signal to traffic_server or is part of the periodic memory logging reports.
> Example:
> {code}
>                                           Location |          Size In-use
> ---------------------------------------------------+------------------------
>                       memory/IOBuffer/FetchSM.h:62 |                 8192
>                       memory/IOBuffer/FetchSM.h:64 |                65536
>                memory/IOBuffer/InkIOCoreAPI.cc:491 |              3346432
>                   memory/IOBuffer/PluginVC.cc:1009 |                65536
>                   memory/IOBuffer/PluginVC.cc:1012 |                    0
>   memory/IOBuffer/ProtocolProbeSessionAccept.cc:39 |              9900032
>           memory/IOBuffer/HttpClientSession.cc:230 |              1703936
>                     memory/IOBuffer/HttpSM.cc:5609 |                16384
>                     memory/IOBuffer/HttpSM.cc:5722 |                    0
>                     memory/IOBuffer/HttpSM.cc:5917 |                    0
>                     memory/IOBuffer/HttpSM.cc:6172 |                    0
>                     memory/IOBuffer/HttpSM.cc:6208 |                    0
>            memory/IOBuffer/HttpServerSession.cc:87 |               516096
>                   memory/IOBuffer/HttpTunnel.cc:95 |                    0
>                  memory/IOBuffer/HttpTunnel.cc:100 |                    0
>                      memory/IOBuffer/Cache.cc:2586 |               765952
>                      memory/IOBuffer/Cache.cc:2600 |            226947072
>                                              TOTAL |            243335168
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)