[
https://issues.apache.org/jira/browse/CASSANDRA-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088116#comment-13088116
]
Hudson commented on CASSANDRA-2594:
-----------------------------------
Integrated in Cassandra #1038 (See
[https://builds.apache.org/job/Cassandra/1038/])
add numactl to java invocation, if available
patch by Peter Schuller; reviewed by Paul Cannon for CASSANDRA-2594
jbellis :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1159834
Files :
* /cassandra/trunk/bin/cassandra
> run cassandra under numactl --interleave=all
> --------------------------------------------
>
> Key: CASSANDRA-2594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2594
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Peter Schuller
> Assignee: Peter Schuller
> Priority: Minor
> Fix For: 1.0
>
> Attachments: CASSANDRA-2594-trunkk.txt
>
>
> By default, Linux attempts to be smart about memory allocations such that
> data is close to the NUMA node on which it runs. For big database type of
> applications, this is not the best thing to do if the priority is to avoid
> disk I/O. In particular with Cassandra, we're heavily multi-threaded anyway
> and there is no particular reason to believe that one NUMA node is "better"
> than another.
> Consequences of allocating unevenly among NUMA nodes can include excessive
> page cache eviction when the kernel tries to allocate memory - such as when
> restarting the JVM.
> With that briefly stated background, I propse the following patch to make the
> Cassandra script run Cassandra with numactl --interleave=all if numactl seems
> to be available.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
