[jira] [Commented] (CASSANDRA-7128) Upgrade NBHM
[ https://issues.apache.org/jira/browse/CASSANDRA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990598#comment-13990598 ] T Jake Luciani commented on CASSANDRA-7128: --- Thanks [~dbrosius] I've opened a ticket on their github https://github.com/boundary/high-scale-lib/issues/7 Upgrade NBHM Key: CASSANDRA-7128 URL: https://issues.apache.org/jira/browse/CASSANDRA-7128 Project: Cassandra Issue Type: Improvement Reporter: T Jake Luciani Assignee: T Jake Luciani Priority: Trivial Labels: performance Fix For: 2.1 rc1 Upgrade NBHM to use the Boundary maintained version -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7128) Upgrade NBHM
[ https://issues.apache.org/jira/browse/CASSANDRA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13989935#comment-13989935 ] Benedict commented on CASSANDRA-7128: - +1 Upgrade NBHM Key: CASSANDRA-7128 URL: https://issues.apache.org/jira/browse/CASSANDRA-7128 Project: Cassandra Issue Type: Improvement Reporter: T Jake Luciani Assignee: T Jake Luciani Priority: Trivial Labels: performance Fix For: 2.1 rc1 Upgrade NBHM to use the Boundary maintained version -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7128) Upgrade NBHM
[ https://issues.apache.org/jira/browse/CASSANDRA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990274#comment-13990274 ] Dave Brosius commented on CASSANDRA-7128: - This patch converts high-scale-lib.jar to one fetched with a maven groupId of com.boundary.high-scale-lib Unfortunately this version of the jar is not available on maven central, but only on http://maven.boundary.com/artifactory/repo What this means if people now try to build from the pom it will fail. try: mvn -f ~/.m2/repository/org/apache/cassandra/cassandra-all/2.1.0-beta2-SNAPSHOT/cassandra-all-2.1.0-beta2-SNAPSHOT.pom dependency:tree to see the problem. The solution is to either 1) add this repo to the published pom or 2) have users who want to build from the pom add the url to their settings.xml file The first one is easier for users, but is discouraged, the second one is more complicated for users, unless they understand what's going on. If we do 2) we should at least document somewhere what needs doing. re-opening, just so we can choose one way or another. Upgrade NBHM Key: CASSANDRA-7128 URL: https://issues.apache.org/jira/browse/CASSANDRA-7128 Project: Cassandra Issue Type: Improvement Reporter: T Jake Luciani Assignee: T Jake Luciani Priority: Trivial Labels: performance Fix For: 2.1 rc1 Upgrade NBHM to use the Boundary maintained version -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7128) Upgrade NBHM
[
https://issues.apache.org/jira/browse/CASSANDRA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990311#comment-13990311
]
Dave Brosius commented on CASSANDRA-7128:
-
settings.xml, needed to build from pom
{code}
settings xmlns=http://maven.apache.org/SETTINGS/1.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd;
profiles
profile
idDefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
repositories
repository
idboundary/id
nameBoundary/name
releases
enabledtrue/enabled
/releases
snapshots
enabledtrue/enabled
/snapshots
urlhttp://maven.boundary.com/artifactory/external//url
layoutdefault/layout
/repository
/repositories
/profile
/profiles
/settings
{code}
Upgrade NBHM
Key: CASSANDRA-7128
URL: https://issues.apache.org/jira/browse/CASSANDRA-7128
Project: Cassandra
Issue Type: Improvement
Reporter: T Jake Luciani
Assignee: T Jake Luciani
Priority: Trivial
Labels: performance
Fix For: 2.1 rc1
Upgrade NBHM to use the Boundary maintained version
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CASSANDRA-7128) Upgrade NBHM
[ https://issues.apache.org/jira/browse/CASSANDRA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986579#comment-13986579 ] Jonathan Ellis commented on CASSANDRA-7128: --- New ticket or ninja? Upgrade NBHM Key: CASSANDRA-7128 URL: https://issues.apache.org/jira/browse/CASSANDRA-7128 Project: Cassandra Issue Type: Improvement Reporter: T Jake Luciani Assignee: T Jake Luciani Priority: Trivial Labels: performance Fix For: 2.1 beta2 Attachments: 7128.txt, Screen Shot 2014-04-30 at 11.07.22 PM.png AbstractRowResolver uses a NBHM for each read request. Profiler flagged this as a bottleneck since the init() call creates a AtomicReferenceFieldUpdater which is stored in a synchronized collection. A NBHS is most certainly overkill for such a short lived object. And turns out switching it to a CHS in my tests yields a ~5-10% read boost. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7128) Upgrade NBHM
[ https://issues.apache.org/jira/browse/CASSANDRA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986640#comment-13986640 ] T Jake Luciani commented on CASSANDRA-7128: --- Can't I use this ticket? I updated the title... Upgrade NBHM Key: CASSANDRA-7128 URL: https://issues.apache.org/jira/browse/CASSANDRA-7128 Project: Cassandra Issue Type: Improvement Reporter: T Jake Luciani Assignee: T Jake Luciani Priority: Trivial Labels: performance Fix For: 2.1 beta2 Attachments: 7128.txt, Screen Shot 2014-04-30 at 11.07.22 PM.png AbstractRowResolver uses a NBHM for each read request. Profiler flagged this as a bottleneck since the init() call creates a AtomicReferenceFieldUpdater which is stored in a synchronized collection. A NBHS is most certainly overkill for such a short lived object. And turns out switching it to a CHS in my tests yields a ~5-10% read boost. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7128) Upgrade NBHM
[ https://issues.apache.org/jira/browse/CASSANDRA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986655#comment-13986655 ] Jonathan Ellis commented on CASSANDRA-7128: --- I thought cleaning out the links and attachments would be more work than a new issue, but go for it Upgrade NBHM Key: CASSANDRA-7128 URL: https://issues.apache.org/jira/browse/CASSANDRA-7128 Project: Cassandra Issue Type: Improvement Reporter: T Jake Luciani Assignee: T Jake Luciani Priority: Trivial Labels: performance Fix For: 2.1 beta2 Attachments: 7128.txt, Screen Shot 2014-04-30 at 11.07.22 PM.png AbstractRowResolver uses a NBHM for each read request. Profiler flagged this as a bottleneck since the init() call creates a AtomicReferenceFieldUpdater which is stored in a synchronized collection. A NBHS is most certainly overkill for such a short lived object. And turns out switching it to a CHS in my tests yields a ~5-10% read boost. -- This message was sent by Atlassian JIRA (v6.2#6252)
