[
https://issues.apache.org/jira/browse/TS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157497#comment-15157497
]
ASF GitHub Bot commented on TS-4212:
------------------------------------
Github user jpeach commented on the pull request:
https://github.com/apache/trafficserver/pull/489#issuecomment-187322502
> What do you mean by duplicates the memory tracking that is already done?
I just meant that the malloc implementation is already tracking the
allocation size.
> Do you know what the overhead is on malloc_usable_size()?
The space overhead will be smaller, since malloc can know things that you
don't and optimize away the need to carry the size with every allocation. For
example, it can know that pointers within a certain range always point to 8
byte chunks.
I expect the time overhead on ``malloc_usable_size`` would be the same or
better.
> 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)
