cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10189) Unify read/writeUTF code paths
Date Sun, 30 Aug 2015 11:37:46 GMT

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

Benedict commented on CASSANDRA-10189:
--------------------------------------

Yes, fallback to a global cache (or, perhaps, a per-cpu cache - or per-hyperthead cache, which
might potentially be maintainable without "atomic" (locked) instructions) - seems a very sensible
approach. But I would prefer we attack that in a followup. We should probably try and ferret
out all occurrences of these kinds of temporary objects and standardize all of them on the
same framework (where suitable).

> Unify read/writeUTF code paths
> ------------------------------
>
>                 Key: CASSANDRA-10189
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10189
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>
> (Follow-up to CASSANDRA-9738 and CASSANDRA-8670)
> CASSANDRA-9738 requires {{writeUTF}} functionality that has been improved in CASSANDRA-8670
plus {{readUTF}} functionality. But we need slightly different signatures - one taking {{DataInput}}/{{DataOutput}}
and one taking {{ByteBuffer}}.
> We can combine both code paths and benefit from a shared, thread-local byte buffer.
> Slightly different implementations are needed for array backed and direct BBs (as we
can directly access the backing array bypassing the direct BB's boundary checks).
> (Part of this has already been done for CASSANDRA-9738 in {{OHCKeyCache.SerializationUtil}})



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

Mime
View raw message