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:
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
Attachments
Issue Links
- is related to
-
TS-1835 Restore ink_resource.{cc,h} functionality
-
- Closed
-