[
https://issues.apache.org/jira/browse/CASSANDRA-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990571#comment-13990571
]
Lyuben Todorov commented on CASSANDRA-6572:
-------------------------------------------
Pushed changes to
[2d9f57d708d67d2c3e191e36daabc2bf35426386|https://github.com/lyubent/cassandra/commit/2d9f57d708d67d2c3e191e36daabc2bf35426386].
The commit deals with:
# Creating the header using a buffer and then writing a Long for the timestamp
and an Int for the query length + bytes of the actual query string
# Switched query frequency to an int
# Moved queryQue (also renamed it to {{queryQueue}}) and {{logPosition}} into a
separate object, also now tracking the {{queryQueue}} with an
{{AtomicReference}}, (still need to swap objects when the log is full rather
than reseting position and emptying the byte[])
# removed {{atomicCounterLock}}
# changed the flush process to using an {{OutputStream}} without looping over
the buffer array.
# stopped looping over arrays when appending to the query buffer, now using
{{System.arrayCopy}} instead.
# changed the workload replay to (still need to read one file at a time, and
break files up into segments)
> Workload recording / playback
> -----------------------------
>
> Key: CASSANDRA-6572
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6572
> Project: Cassandra
> Issue Type: New Feature
> Components: Core, Tools
> Reporter: Jonathan Ellis
> Assignee: Lyuben Todorov
> Fix For: 2.1.1
>
> Attachments: 6572-trunk.diff
>
>
> "Write sample mode" gets us part way to testing new versions against a real
> world workload, but we need an easy way to test the query side as well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
