[
https://issues.apache.org/jira/browse/AXIS2-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232543#comment-13232543
]
Shameera Rathnayaka commented on AXIS2-5270:
--------------------------------------------
Hi devs ,
I have tried a few performance tests with current SOAP procedure vs implemented
Json procedure with java bench tool. Here is the summarized results of what i
received. I have attached the sample service jsonTestService.aar ( This is the
same service which is attached with my first reply but have done few minor
modifications) used for this test.
Note: i have restarted axis2 server before run each test, to avoid effect of
caching.
1. Send 1000 requests to the echoUser method in the service with same user
object which has exactly the same fields in both procedure.
Json Implementation
SOAP
Server Software: Simple-Server/1.1
Simple-Server/1.1
Document Path: http://localhost:8080/axis2/services/
http://localhost:8080/axis2/services/
JsonTestService/echoUser
JsonTestService.JsonTestServiceHttpSoap11Endpoint/
Document Length: 231 bytes
795 bytes
Concurrency Level: 1
1
Time taken for tests: 2.648290 seconds
3.551833 seconds
Complete requests: 1000
1000
Total transferred: 472000 bytes
1659000 bytes
Requests per second: 377.60 [#/sec] (mean)
281.54 [#/sec] (mean)
Time per request: 2.648 [ms] (mean)
3.552 [ms] (mean)
Transfer rate: 87.23 [Kbytes/sec] received
223.83 [Kbytes/sec] received
91.00 kb/s sent
243.25 kb/s sent
2. Send 1000 requests to the addUserList method in the service with list of
1000 users.
Json Implementation
SOAP
Server Software: Simple-Server/1.1
Simple-Server/1.1
Document Path: http://localhost:8080/axis2/services/
http://localhost:8080/axis2/services/
JsonTestService/addUserList
JsonTestService.JsonTestServiceHttpSoap11Endpoint/
Document Length: 17 bytes
276 bytes
Concurrency Level: 1
1
Time taken for tests: 7.669473 seconds
27.230592 seconds
Complete requests: 1000
1000
Total transferred: 219052000 bytes
401567000 bytes
Requests per second: 130.39 [#/sec] (mean)
36.72 [#/sec] (mean)
Time per request: 7.669 [ms] (mean)
27.231 [ms] (mean)
Transfer rate: 2.22 [Kbytes/sec] received
10.14 [Kbytes/sec] received
28,559.33 kb/s sent
14,736.77 kb/s sent
> [GSOC 2012] Improve Json support in Axis2 with google-gson
> ----------------------------------------------------------
>
> Key: AXIS2-5270
> URL: https://issues.apache.org/jira/browse/AXIS2-5270
> Project: Axis2
> Issue Type: Improvement
> Components: json
> Affects Versions: 1.7.0
> Reporter: Shameera Rathnayaka
> Assignee: Shameera Rathnayaka
> Labels: gsoc2012, gson, json
> Fix For: 1.7.0
>
> Attachments: attachments.zip
>
>
> There are two ways that xml string can be converted into JSON string,
> Badgerfish and Mapped . Current Axis2 with JSON module completely supports
> Badgerfish convention[1] while partialy supports Mapped convention[1] as
> Mapped formatted JSON with namespaces are not supported in Axis2. Therefore
> if the client side java-script code needs to talk with java service which is
> deployed in Axis2, it should be sent as Badgerfish convention. It is
> cumbersome to generate Badgerfish convention of JSON string again and again
> to call services if there is no xml representation string in client side.
> If java script client can send JSON object to relevant java service in Axis2,
> defining service and operation in request url, without doing any
> modifications to JSON objects, then it would be very helpful for Java-Script
> users at client side.
> According to the thread in the mailing list, which discussed $subject we have
> two approaches. i have summarized those two approaches as below.
> 1. Store json inputstream in message context at the message builder while
> putting dummy SOAPEnvelop to the message context, and using google-gson
> process it inside the message receiver
> 2. Preserve the requirement that a message must have a well defined SOAP
> infoset and use a trivial representation similar (or identical) to what we
> use for plain text. This has the advantage that it is more in line with the
> rest of the Axis2 architecture,
> or
> another option is to write an xmlstream reader/writer implementation to
> parse the json stream. And provide that xml stream implementation to Axiom.
> [1]http://wso2.org/library/768
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
