cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9197) Startup slowdown due to preloading jemalloc
Date Tue, 21 Apr 2015 07:55:03 GMT

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

Sylvain Lebresne commented on CASSANDRA-9197:
---------------------------------------------

bq. hardcoding the path as you stated does improve the startup time

Out of curiosity, does it make it like without jemalloc? In other words, is it the {{find_library}}
method that improve the startup time, or is it both that and loading jemalloc?

> Startup slowdown due to preloading jemalloc
> -------------------------------------------
>
>                 Key: CASSANDRA-9197
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9197
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Philip Thompson
>            Priority: Minor
>
> On my box, it seems that the jemalloc loading from CASSANDRA-8714 made the process take
~10 seconds to even start (I have no explication for it). I don't know if it's specific to
my machine or not, so that ticket is mainly so someone else can check if it sees the same,
in particular for jenkins. If it does sees the same slowness, we might want to at least disable
jemalloc for dtests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message