cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11517) o.a.c.utils.UUIDGen could handle contention better
Date Fri, 06 May 2016 15:48:13 GMT

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

Ariel Weisberg commented on CASSANDRA-11517:
--------------------------------------------

Thanks for catching that test bug (again), fixing the comparison, and running it through JMH.
Your changes LGTM.

> o.a.c.utils.UUIDGen could handle contention better
> --------------------------------------------------
>
>                 Key: CASSANDRA-11517
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11517
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Ariel Weisberg
>            Assignee: Ariel Weisberg
>            Priority: Minor
>             Fix For: 3.x
>
>
> I noticed this profiling a query handler implementation that uses UUIDGen to get handles
to track queries for logging purposes.
> Under contention threads are being unscheduled instead of spinning until the lock is
available. I would have expected intrinsic locks to be able to adapt to this based on profiling
information.
> Either way it's seems pretty straightforward to rewrite this to use a CAS loop and test
that it generally produces unique values.



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

Mime
View raw message