[ 
https://issues.apache.org/jira/browse/IMPALA-15021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18087722#comment-18087722
 ] 

ASF subversion and git services commented on IMPALA-15021:
----------------------------------------------------------

Commit aac753cb3208effb6f41f916b53a17a05ed967c6 in impala's branch 
refs/heads/master from Joe McDonnell
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=aac753cb3 ]

IMPALA-15021: Remove duplicate tcmalloc.thread_cache_free_bytes metric

In IMPALA-14874, we introduced several tcmalloc metrics
including tcmalloc.current-total-thread-cache-bytes and
tcmalloc.thread-cache-free-bytes. These are actually the
same underlying metric, so this removes tcmalloc.thread-cache-free-bytes.

Testing:
 - Ran core tests

Change-Id: I7ff431b00c10fe9ff99bfd6c909739d8a97fcf3a
Reviewed-on: http://gerrit.cloudera.org:8080/24399
Reviewed-by: Michael Smith <[email protected]>
Reviewed-by: Csaba Ringhofer <[email protected]>
Tested-by: Joe McDonnell <[email protected]>


> Remove one of the gperftools tcmalloc thread cache metrics
> ----------------------------------------------------------
>
>                 Key: IMPALA-15021
>                 URL: https://issues.apache.org/jira/browse/IMPALA-15021
>             Project: IMPALA
>          Issue Type: Task
>          Components: Backend
>    Affects Versions: Impala 5.0.0
>            Reporter: Joe McDonnell
>            Priority: Minor
>
> In IMPALA-14874, we added additional gperftools TCMalloc metrics. This 
> included both tcmalloc.current-total-thread-cache-bytes and 
> tcmalloc.thread-cache-free-bytes, which map down to the gperftools metrics 
> tcmalloc.current_total_thread_cache_bytes and 
> tcmalloc.thread_cache_free_bytes respectively. Inside the gperftools code, 
> these are actually the same counter, so we can remove one.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to