[
https://issues.apache.org/jira/browse/TS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157445#comment-15157445
]
ASF GitHub Bot commented on TS-4212:
------------------------------------
Github user bryancall commented on the pull request:
https://github.com/apache/trafficserver/pull/489#issuecomment-187310269
@jpeach
I don't think it can get less ugly. I tried to clean it up as much as
possible.
What do you mean by duplicates the memory tracking that is already done?
There is no memory tracking for OpenSSL right now. This is how I was able to
see an issue with OpenSSL memory usage in our production environment and
resolve the issue.
Is there an issue with memory alignment and is there a performance concern
if we are using this as a diagnostic tool?
> Add option to track memory allocation with OpenSSL
> --------------------------------------------------
>
> Key: TS-4212
> URL: https://issues.apache.org/jira/browse/TS-4212
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, SSL
> Reporter: Bryan Call
> Fix For: 6.2.0
>
>
> For example:
> {code}
> [bcall@l1 ~]$ sudo traffic_line -s proxy.config.res_track_memory -v 2
> [bcall@l1 ~]$ sudo kill -sigusr1 $(pidof traffic_server); tail traffic.out
> Total Allocated | Total Freed | Currently Allocated | Type
> ---------------------|----------------------|----------------------|----------------------
> 18437960662 | 17181254510 | 1256706152 | SSL
> Allocated Memory
> ---------------------|----------------------|----------------------|----------------------
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
