[
https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748219#comment-13748219
]
Dishara Wijewardana commented on SLING-3026:
--------------------------------------------
First round of report in brief: P.S This results based on very first time
retrieval of these nodes.
1. http://localhost:8080/content/cassandra/A/100.json - Time per request:
65.449 [ms]
2. http://localhost:8080/content/cassandra/B/100.json - Time per request:
73.022 [ms]
3. http://localhost:8080/content/cassandra/C/100.json - Time per request:
61.696 [ms]
4. http://localhost:8080/content/cassandra/D/100.json - Time per request:
71.855 [ms]
> Cassandra Resource Provider READ Latency Stats
> -----------------------------------------------
>
> Key: SLING-3026
> URL: https://issues.apache.org/jira/browse/SLING-3026
> Project: Sling
> Issue Type: Task
> Reporter: Dishara Wijewardana
> Priority: Critical
> Attachments: SLING_CASSANDRA_LATENCY_STATS_22-08-2013.txt
>
>
> This is to keep track on the statistics of the latency for the requests done
> on Cassandra layer through Cassandra Resource Provider. Here we use Apache
> Benchmark.
> We have a test profile java component in the cassandra module to add bulk
> test data to cassandra.
> /content/cassandra/A/0 to /content/cassandra/A/999
> /content/cassandra/B/0 to /content/cassandra/B/9999
> /content/cassandra/C/0 to /content/cassandra/C/99999
> /content/cassandra/D/0 to /content/cassandra/D/999999
> And then this JIRA will keep track of reports on the http request time to
> retrieve 1 node from each following data collection.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
