[
https://issues.apache.org/jira/browse/CASSANDRA-13031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795456#comment-15795456
]
Corentin Chary commented on CASSANDRA-13031:
--------------------------------------------
You can look for "Completed flushing" in debug.log and you'll get the timestamp
of the left (thus the time spent doing these operations). You should see that
each flush takes 500-300ms and each of the individual changes will remove this
pause of hundred of ms. For those that need to do a read query they will take
<1ms instead.
I will re-run this with your patch tomorrow morning.
> Speed-up start-up sequence by avoiding un-needed flushes
> --------------------------------------------------------
>
> Key: CASSANDRA-13031
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13031
> Project: Cassandra
> Issue Type: Bug
> Reporter: Corentin Chary
> Assignee: Corentin Chary
> Priority: Minor
> Fix For: 3.x
>
> Attachments: 0001-Avoid-un-needed-system-flushes-on-startup.patch,
> debug-fast.log, debug.log, debug_130131.diff, debug_130131_2.diff
>
>
> Similar to CASSANDRA-12969, do a conditional update for all functions
> with a forced blocking flush to avoid slowed-down boot sequences. The
> small performance hit of doing a read is always smaller than the one
> associated with a fsync().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
