cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3997) Make SerializingCache Memory Pluggable
Date Mon, 26 Mar 2012 16:48:27 GMT

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

Vijay commented on CASSANDRA-3997:
----------------------------------

>>> Vijay, can you please also test Hoard Memory Allocator (http://www.hoard.org/)
as a comparison to jemalloc?
Sure, but looks like LD_PRELOAD causes crashes due to various reasons and doesn't sound like
a good solution. I will check in the mailing list about the same.

[vijay_tcasstest@vijay_tcass-i-a91ee8cd crash]$ grep -A2 Problematic *
hs_err_pid1309.log:# Problematic frame:
hs_err_pid1309.log-# C  [libjemalloc.so+0xb79a]
hs_err_pid1309.log-#
--
hs_err_pid1622.log:# Problematic frame:
hs_err_pid1622.log-# C  [libjemalloc.so+0x57f4]  free+0x54
hs_err_pid1622.log-#
--
hs_err_pid16902.log:# Problematic frame:
hs_err_pid16902.log-# C  [libjemalloc.so+0xb79a]
hs_err_pid16902.log-[error occurred during error reporting (printing problematic frame), id
0xb]
--
hs_err_pid16902.log:# Problematic frame:
hs_err_pid16902.log-# C  [libjemalloc.so+0xb79a]
hs_err_pid16902.log-[error occurred during error reporting (printing problematic frame), id
0xb]
--
hs_err_pid29892.log:# Problematic frame:
hs_err_pid29892.log-# C  [libjemalloc.so+0xb79a]
hs_err_pid29892.log-#
--
hs_err_pid30273.log:# Problematic frame:
hs_err_pid30273.log-# C  [libjemalloc.so+0xb79a]
hs_err_pid30273.log-#
--
hs_err_pid30645.log:# Problematic frame:
hs_err_pid30645.log-# C  [libjemalloc.so+0xb79a]
hs_err_pid30645.log-#
--
hs_err_pid4037.log:# Problematic frame:
hs_err_pid4037.log-# C  [libjemalloc.so+0xb79a]
hs_err_pid4037.log-[error occurred during error reporting (printing problematic frame), id
0xb]
--
hs_err_pid7733.log:# Problematic frame:
hs_err_pid7733.log-# C  [libc.so.6+0x618a2]
hs_err_pid7733.log-[error occurred during error reporting (printing problematic frame), id
0xb]
--
hs_err_pid7733.log:# Problematic frame:
hs_err_pid7733.log-# C  [libc.so.6+0x618a2]
hs_err_pid7733.log-[error occurred during error reporting (printing problematic frame), id
0xb]
                
> Make SerializingCache Memory Pluggable
> --------------------------------------
>
>                 Key: CASSANDRA-3997
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3997
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>              Labels: cache
>             Fix For: 1.2
>
>         Attachments: 0001-CASSANDRA-3997.patch, jna.zip
>
>
> Serializing cache uses native malloc and free by making FM pluggable, users will have
a choice of gcc malloc, TCMalloc or JEMalloc as needed. 
> Initial tests shows less fragmentation in JEMalloc but the only issue with it is that
(both TCMalloc and JEMalloc) are kind of single threaded (at-least they crash in my test otherwise).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message