[ 
http://issues.apache.org/jira/browse/XMLRPC-119?page=comments#action_12442604 ] 
            
Steve Morin commented on XMLRPC-119:
------------------------------------

Ran a few more tests over the weekend.

Try the test 
instead of - 
public static class XMLRPC119Handler {
        /** Returns a string with a length of "num" Kilobytes.
         */
        public String getString(int pSize) {
            StringBuffer sb = new StringBuffer(pSize*1024);
            for (int i = 0; i < pSize*1024; i++) {
                sb.append('0');
            }
            return sb.toString();
        }
    } 

public static class XMLRPC120Handler {
        /** Returns a string with a length of "num" Kilobytes.
         */
        public String getString(int pSize) {
            StringBuffer sb = new StringBuffer(pSize*1024);
            for (int i = 0; i < pSize*1024; i++) {
                sb.append('/');
            }
            return sb.toString();
        }
    } 

This should give you a much slower result


> very slow client when transmitting strings more than 15k
> --------------------------------------------------------
>
>                 Key: XMLRPC-119
>                 URL: http://issues.apache.org/jira/browse/XMLRPC-119
>             Project: XML-RPC
>          Issue Type: Bug
>          Components: Releases, Source
>    Affects Versions: 3.0b1
>         Environment: linux debian sun jdk 1.5 
> mac osx tiger sun jdk 1.5
>            Reporter: Steve Morin
>
> Using xmlrpc java library as both client and server.
> The problem boiles down to this we are using xmlrpc(3.0b1) to return a
> xml document as a string.  
> Client tries to recieve the string
>    12k file takes 100ms
>    75k file takes about 3 minutes
> Using python xmlrpc client instead of Java
>    12k file takes 100ms
>    75k file takes 400ms
> Double check the timing and ruled out the server or network being a problem 
> using a number of different
> test on various machines.
> I tried to check for this problem in the jira issue tracker but didn't
> find any mention of this problem.
> Also we tried using different machines to test this problem and duplicated 
> the content of the 12k file to rule out the problem being 
> related to the content of original 75k file vs the different content of the 
> 12k file.
> We didn't do an incremental test to find out if there is a break point the 
> performance degrades dramatically.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to