[jira] [Updated] (SLING-2798) Apache Cassandra backend for Sling: GSoC2013 Project
[ https://issues.apache.org/jira/browse/SLING-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dishara Wijewardana updated SLING-2798: --- Attachment: cassandra-backend-for-sling.tar.gz Attaching the source archive in order to donate the GSoC source code to Apache Sling. > Apache Cassandra backend for Sling: GSoC2013 Project > > > Key: SLING-2798 > URL: https://issues.apache.org/jira/browse/SLING-2798 > Project: Sling > Issue Type: Bug > Components: Samples >Reporter: Ian Boston > Labels: cassandra, gsoc, gsoc2013, java, osgi, sling > Attachments: cassandra-backend-for-sling.tar.gz, Sling Cassandra > backend Architecture.jpg > > > This is a proposal for GSoC2013: create an Resource Provider that allows > resources stored in Apache Cassandra to be exposed as Sling Resources. > Resources[1] are the basic building blocks of Sling. > ResourceProviders[2] allow data sources to be added to the core > ResourceProvider within Sling allowing those data sources to provide > Resources at pre-determined locations in the resource tree. To put it in more > familiar terms, implementing and adding a Resource provider is like mounting > or mapping a network drive. > A more recent addition to the facilities available in Sling include updatable > ResourceProviders. > Apache Cassandra[3] is a column database (NoSQL) which aims to provide linear > scalability to web scale. It is used by many of the best known names on the > internet. > Initially this will provide read only resource access, but if there is time > in the project will allow read write access to a cassandra cluster. > Advanced Java skills are required, some knowledge of OSGi, Sling, Cassandra > will be valuable. > The following pages give more information about GSoC @apache: > * http://www.google-melange.com/gsoc/homepage/google/gsoc2013 > * http://community.apache.org/gsoc.html > * http://s.apache.org/gsoc2013ideas > 1 http://sling.apache.org/site/resources.html > 2 > http://sling.apache.org/apidocs/sling6/org/apache/sling/api/resource/ResourceProvider.html > 3 http://cassandra.apache.org/ -- 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
[jira] [Updated] (SLING-3026) Cassandra Resource Provider READ Latency Stats
[ https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dishara Wijewardana updated SLING-3026: --- Attachment: results.zip This Zip contains latest test runs. The Difference is for each Node, separate report is created. > 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: CassandraCreateLatencyReport.txt, > CassandraDeleteLatencyReport.txt, CassandraIntegrationTest.patch, > CassandraLatencyReport.txt, CassandraLatencyReport_V1.txt, > CassandraUpdateLatencyReport.txt, CUD_Latency_Report-11-09-13.zip, > results.zip, SLING_CASSANDRA_LATENCY_STATS_22-08-2013.txt, > SLING_CASSANDRA_LATENCY_STATS_CHART_22-08-2013.png, > SLING_CASSANDRA_LATENCY_STATS_TWO_CHART_22-08-2013.png > > > 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/ > /content/cassandra/C/0 to /content/cassandra/C/9 > /content/cassandra/D/0 to /content/cassandra/D/99 > 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
[jira] [Updated] (SLING-3026) Cassandra Resource Provider READ Latency Stats
[ https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dishara Wijewardana updated SLING-3026: --- Attachment: CUD_Latency_Report-11-09-13.zip Hi Here are the latest CUD results which done on pre populated collections > 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: CassandraCreateLatencyReport.txt, > CassandraDeleteLatencyReport.txt, CassandraIntegrationTest.patch, > CassandraLatencyReport.txt, CassandraLatencyReport_V1.txt, > CassandraUpdateLatencyReport.txt, CUD_Latency_Report-11-09-13.zip, > SLING_CASSANDRA_LATENCY_STATS_22-08-2013.txt, > SLING_CASSANDRA_LATENCY_STATS_CHART_22-08-2013.png, > SLING_CASSANDRA_LATENCY_STATS_TWO_CHART_22-08-2013.png > > > 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/ > /content/cassandra/C/0 to /content/cassandra/C/9 > /content/cassandra/D/0 to /content/cassandra/D/99 > 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
[jira] [Updated] (SLING-3026) Cassandra Resource Provider READ Latency Stats
[ https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dishara Wijewardana updated SLING-3026: --- Attachment: CassandraUpdateLatencyReport.txt CassandraDeleteLatencyReport.txt CassandraCreateLatencyReport.txt Here I am atttaching CUD Cassandra Perf data sheets. > 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: CassandraCreateLatencyReport.txt, > CassandraDeleteLatencyReport.txt, CassandraIntegrationTest.patch, > CassandraLatencyReport.txt, CassandraLatencyReport_V1.txt, > CassandraUpdateLatencyReport.txt, > SLING_CASSANDRA_LATENCY_STATS_22-08-2013.txt, > SLING_CASSANDRA_LATENCY_STATS_CHART_22-08-2013.png, > SLING_CASSANDRA_LATENCY_STATS_TWO_CHART_22-08-2013.png > > > 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/ > /content/cassandra/C/0 to /content/cassandra/C/9 > /content/cassandra/D/0 to /content/cassandra/D/99 > 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
[jira] [Updated] (SLING-3026) Cassandra Resource Provider READ Latency Stats
[ https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dishara Wijewardana updated SLING-3026: --- Attachment: CassandraLatencyReport_V1.txt Here I am attaching the latest test results which includes latency to pull data from a 10M and 100M collections. > 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: CassandraIntegrationTest.patch, > CassandraLatencyReport.txt, CassandraLatencyReport_V1.txt, > SLING_CASSANDRA_LATENCY_STATS_22-08-2013.txt, > SLING_CASSANDRA_LATENCY_STATS_CHART_22-08-2013.png, > SLING_CASSANDRA_LATENCY_STATS_TWO_CHART_22-08-2013.png > > > 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/ > /content/cassandra/C/0 to /content/cassandra/C/9 > /content/cassandra/D/0 to /content/cassandra/D/99 > 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
[jira] [Updated] (SLING-3026) Cassandra Resource Provider READ Latency Stats
[ https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dishara Wijewardana updated SLING-3026: --- Attachment: CassandraLatencyReport.txt Please find the attached Latency report with latest model. > 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: CassandraIntegrationTest.patch, > CassandraLatencyReport.txt, SLING_CASSANDRA_LATENCY_STATS_22-08-2013.txt, > SLING_CASSANDRA_LATENCY_STATS_CHART_22-08-2013.png, > SLING_CASSANDRA_LATENCY_STATS_TWO_CHART_22-08-2013.png > > > 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/ > /content/cassandra/C/0 to /content/cassandra/C/9 > /content/cassandra/D/0 to /content/cassandra/D/99 > 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
[jira] [Updated] (SLING-3026) Cassandra Resource Provider READ Latency Stats
[ https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dishara Wijewardana updated SLING-3026: --- Attachment: CassandraIntegrationTest.patch Here I am attaching the patch which has the integration test for Cassandra Load Test > 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: CassandraIntegrationTest.patch, > CassandraLatencyReport.txt, SLING_CASSANDRA_LATENCY_STATS_22-08-2013.txt, > SLING_CASSANDRA_LATENCY_STATS_CHART_22-08-2013.png, > SLING_CASSANDRA_LATENCY_STATS_TWO_CHART_22-08-2013.png > > > 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/ > /content/cassandra/C/0 to /content/cassandra/C/9 > /content/cassandra/D/0 to /content/cassandra/D/99 > 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
[jira] [Updated] (SLING-3026) Cassandra Resource Provider READ Latency Stats
[ https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dishara Wijewardana updated SLING-3026: --- Attachment: SLING_CASSANDRA_LATENCY_STATS_TWO_CHART_22-08-2013.png SLING_CASSANDRA_LATENCY_STATS_CHART_22-08-2013.png The corresponding graphs attach herewith. > 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, > SLING_CASSANDRA_LATENCY_STATS_CHART_22-08-2013.png, > SLING_CASSANDRA_LATENCY_STATS_TWO_CHART_22-08-2013.png > > > 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/ > /content/cassandra/C/0 to /content/cassandra/C/9 > /content/cassandra/D/0 to /content/cassandra/D/99 > 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
[jira] [Comment Edited] (SLING-3026) Cassandra Resource Provider READ Latency Stats
[ https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748219#comment-13748219 ] Dishara Wijewardana edited comment on SLING-3026 at 8/23/13 2:23 AM: - First round of report in brief: P.S This results based on very first time retrieval of these nodes (with in a single server startup). 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] Same round of test results, but each node retrieval done in a fresh server start. 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: 236.641 [ms] 3. http://localhost:8080/content/cassandra/C/100.json - Time per request: 260.856 [ms] 4. http://localhost:8080/content/cassandra/D/100.json - Time per request: 233.855 [ms] was (Author: ddwijewardana): 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/ > /content/cassandra/C/0 to /content/cassandra/C/9 > /content/cassandra/D/0 to /content/cassandra/D/99 > 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
[jira] [Commented] (SLING-3026) Cassandra Resource Provider READ Latency Stats
[ 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/ > /content/cassandra/C/0 to /content/cassandra/C/9 > /content/cassandra/D/0 to /content/cassandra/D/99 > 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
[jira] [Updated] (SLING-3026) Cassandra Resource Provider READ Latency Stats
[ https://issues.apache.org/jira/browse/SLING-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dishara Wijewardana updated SLING-3026: --- Attachment: SLING_CASSANDRA_LATENCY_STATS_22-08-2013.txt Here I have attached the first round of report. > 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/ > /content/cassandra/C/0 to /content/cassandra/C/9 > /content/cassandra/D/0 to /content/cassandra/D/99 > 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
[jira] [Created] (SLING-3026) Cassandra Resource Provider READ Latency Stats
Dishara Wijewardana created SLING-3026: -- Summary: 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 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/ /content/cassandra/C/0 to /content/cassandra/C/9 /content/cassandra/D/0 to /content/cassandra/D/99 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
[jira] [Updated] (SLING-2798) Apache Cassandra backend for Sling: GSoC2013 Project
[ https://issues.apache.org/jira/browse/SLING-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dishara Wijewardana updated SLING-2798: --- Attachment: Sling Cassandra backend Architecture.jpg > Apache Cassandra backend for Sling: GSoC2013 Project > > > Key: SLING-2798 > URL: https://issues.apache.org/jira/browse/SLING-2798 > Project: Sling > Issue Type: Bug > Components: Samples >Reporter: Ian Boston > Labels: cassandra, gsoc, gsoc2013, java, osgi, sling > Attachments: Sling Cassandra backend Architecture.jpg > > > This is a proposal for GSoC2013: create an Resource Provider that allows > resources stored in Apache Cassandra to be exposed as Sling Resources. > Resources[1] are the basic building blocks of Sling. > ResourceProviders[2] allow data sources to be added to the core > ResourceProvider within Sling allowing those data sources to provide > Resources at pre-determined locations in the resource tree. To put it in more > familiar terms, implementing and adding a Resource provider is like mounting > or mapping a network drive. > A more recent addition to the facilities available in Sling include updatable > ResourceProviders. > Apache Cassandra[3] is a column database (NoSQL) which aims to provide linear > scalability to web scale. It is used by many of the best known names on the > internet. > Initially this will provide read only resource access, but if there is time > in the project will allow read write access to a cassandra cluster. > Advanced Java skills are required, some knowledge of OSGi, Sling, Cassandra > will be valuable. > The following pages give more information about GSoC @apache: > * http://www.google-melange.com/gsoc/homepage/google/gsoc2013 > * http://community.apache.org/gsoc.html > * http://s.apache.org/gsoc2013ideas > 1 http://sling.apache.org/site/resources.html > 2 > http://sling.apache.org/apidocs/sling6/org/apache/sling/api/resource/ResourceProvider.html > 3 http://cassandra.apache.org/ -- 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
