[jira] [Commented] (DISPATCH-511) Remove performance problems from locks and memory allocation
[ https://issues.apache.org/jira/browse/DISPATCH-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506751#comment-15506751 ] ASF subversion and git services commented on DISPATCH-511: -- Commit 5b09760d0d3637978ca3770c677e640837076727 in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=5b09760 ] DISPATCH-511 - Fixed issue with posix_memalign's return value being ignored. > Remove performance problems from locks and memory allocation > > > Key: DISPATCH-511 > URL: https://issues.apache.org/jira/browse/DISPATCH-511 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Reporter: Ted Ross >Assignee: Ted Ross > Fix For: 0.7.0 > > > There are a number of performance issues with locks and memory pooling: > - Locks are not allocated on cache-line boundaries and suffer from > false-sharing issues. > - The extra lock checks (checking the acquired state) cause significant > overhead. These should be removed. > - Pooled memory objects are not cache-line aligned and suffer from > false-sharing > - Memory pool statistics are useful but costly from a performance > standpoint. These should be able to be optionally disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-511) Remove performance problems from locks and memory allocation
[ https://issues.apache.org/jira/browse/DISPATCH-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494521#comment-15494521 ] ASF subversion and git services commented on DISPATCH-511: -- Commit 566a1a19e2c662b40aa4477421bddb51e4e7310c in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=566a1a1 ] DISPATCH-511 - Cache-line align mutexes and conditions. Remove extra assertions in mutexes. > Remove performance problems from locks and memory allocation > > > Key: DISPATCH-511 > URL: https://issues.apache.org/jira/browse/DISPATCH-511 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Reporter: Ted Ross >Assignee: Ted Ross > Fix For: 0.7.0 > > > There are a number of performance issues with locks and memory pooling: > - Locks are not allocated on cache-line boundaries and suffer from > false-sharing issues. > - The extra lock checks (checking the acquired state) cause significant > overhead. These should be removed. > - Pooled memory objects are not cache-line aligned and suffer from > false-sharing > - Memory pool statistics are useful but costly from a performance > standpoint. These should be able to be optionally disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-511) Remove performance problems from locks and memory allocation
[ https://issues.apache.org/jira/browse/DISPATCH-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494522#comment-15494522 ] ASF subversion and git services commented on DISPATCH-511: -- Commit 375aec4a52de846716f202b2a066e76d8d86eb7a in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=375aec4 ] DISPATCH-511 - Make memory-pool statistics enableable by configuration (defaults to ON). > Remove performance problems from locks and memory allocation > > > Key: DISPATCH-511 > URL: https://issues.apache.org/jira/browse/DISPATCH-511 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Reporter: Ted Ross >Assignee: Ted Ross > Fix For: 0.7.0 > > > There are a number of performance issues with locks and memory pooling: > - Locks are not allocated on cache-line boundaries and suffer from > false-sharing issues. > - The extra lock checks (checking the acquired state) cause significant > overhead. These should be removed. > - Pooled memory objects are not cache-line aligned and suffer from > false-sharing > - Memory pool statistics are useful but costly from a performance > standpoint. These should be able to be optionally disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-511) Remove performance problems from locks and memory allocation
[ https://issues.apache.org/jira/browse/DISPATCH-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494517#comment-15494517 ] Ted Ross commented on DISPATCH-511: --- Memory pool statistics are enabled by default. If you wish to disable them for improved performance, use the following cmake definition: cmake -DQD_MEMORY_STATS=OFF .. > Remove performance problems from locks and memory allocation > > > Key: DISPATCH-511 > URL: https://issues.apache.org/jira/browse/DISPATCH-511 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Reporter: Ted Ross >Assignee: Ted Ross > Fix For: 0.7.0 > > > There are a number of performance issues with locks and memory pooling: > - Locks are not allocated on cache-line boundaries and suffer from > false-sharing issues. > - The extra lock checks (checking the acquired state) cause significant > overhead. These should be removed. > - Pooled memory objects are not cache-line aligned and suffer from > false-sharing > - Memory pool statistics are useful but costly from a performance > standpoint. These should be able to be optionally disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
