[jira] [Commented] (JCLOUDS-358) Improve blob request signing performance

["Shri Javadekar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCLOUDS-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826058#comment-13826058 ] 

Shri Javadekar commented on JCLOUDS-358:
----------------------------------------

The problem here seemed bloated because of the way Yourkit was used. YourKit was configured to trace every single function call; i.e entry and exit of every function call was instrumented. The URL signing code goes through layers and layers of such calls. That seemed to have bloated the numbers. Even in my latest test run with YourKit, I saw the each url signing request for aws-s3 was taking an average time of 10 ms.

Instead of using YourKit, I simply added a stopwatch in the code and logged the time required for signing the urls. Without YourKit, the time required for signing each request was less than 1 ms.

> Improve blob request signing performance
> ----------------------------------------
>
>                 Key: JCLOUDS-358
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-358
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-blobstore
>    Affects Versions: 1.6.3
>            Reporter: Shri Javadekar
>             Fix For: 1.7.0
>
>
> I ran an application which calls into jclouds for signing blob put requests (against the aws-s3 blobstore) and analyzed its performance using YourKit. The analysis shows that each request for signing blobs takes about 13 ms (average of 160K requests). > 10 out of these 13 ms are spent in the RestAnnotationProcessor. Mainly in RestAnnotationProcessor.apply() and RestAnnotationProcessor.decorateRequest(). Looking at the code, it seems that processing of all the annotations is done for every request, which also means that there is the Java Reflections overhead for every request.
> Are there options that we can explore to make this better; such as 
>  i) caching the output of the RestAnnotationProcessor and only updating fields that change in every request
> ii) not using java Reflections API
> Note that I am using jclouds-1.6.3-SNAPSHOT which includes the fixes for bug 301.
> https://issues.apache.org/jira/browse/JCLOUDS-301



--
This message was sent by Atlassian JIRA
(v6.1#6144)