[
https://issues.apache.org/jira/browse/CASSANDRA-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-4282:
--------------------------------------
Attachment: 4282-v2.txt
v2 takes the approach of modifying CacheSerializer.deserialize to return a
Future. The row values are read on the read Stage instead of creating a new
ExecutorService.
> Improve startup time by making row cache population multi threaded
> ------------------------------------------------------------------
>
> Key: CASSANDRA-4282
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4282
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Priority: Minor
> Fix For: 1.2.0
>
> Attachments:
> 0001-improve-startup-time-by-multi-threading-row-cache-re.patch, 4282-v2.txt
>
>
> Attached patch multi threads the row cache population
> my small tests show improvements atleast;
> {code}
> - 4 cores
>
>
> - 11G stress-generated data
> - page cache dropped between runs
>
>
>
>
>
> single platter spinning disk:
>
>
> single threaded:
>
>
> INFO 10:18:21,365 completed loading (245562 ms; 311381 keys) row cache for
> Keyspace1.Standard1
>
> INFO 10:32:43,738 completed loading (255106 ms; 311381 keys) row cache for
> Keyspace1.Standard1
>
> multi threaded:
>
>
> INFO 10:22:47,567 completed loading (213905 ms; 311381 keys) row cache for
> Keyspace1.Standard1
>
> INFO 10:27:26,873 completed loading (214514 ms; 311381 keys) row cache for
> Keyspace1.Standard1
>
>
>
>
> ssd;
>
>
> single threaded:
>
>
> INFO 10:40:49,079 completed loading (103883 ms; 311381 keys) row cache for
> Keyspace1.Standard1
>
> INFO 10:43:45,799 completed loading (106913 ms; 311381 keys) row cache for
> Keyspace1.Standard1
>
> multi threaded:
>
>
> INFO 10:38:20,798 completed loading (57617 ms; 311381 keys) row cache for
> Keyspace1.Standard1
>
> INFO 10:47:20,339 completed loading (56682 ms; 311381 keys) row cache for
> Keyspace1.Standard1
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
