[
http://issues.apache.org/jira/browse/XMLRPC-119?page=comments#action_12441847 ]
Jochen Wiedmann commented on XMLRPC-119:
----------------------------------------
I can't reproduce your problem. My test looks like this:
/**
* Test case for <a href="http://issues.apache.org/jira/browse/XMLRPC-119";>
* XMLRPC-119</a>
*/
public void testXMLRPC119() throws Exception {
for (int i = 0; i < providers.length; i++) {
testXMLRPC119(providers[i]);
}
}
/** Handler for XMLRPC-119
*/
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();
}
}
private void testXMLRPC119(ClientProvider pProvider) throws Exception {
XmlRpcClient client = pProvider.getClient();
client.setConfig(getConfig(pProvider));
for (int i = 0; i < 100; i+= 10) {
long now = System.currentTimeMillis();
String s = (String) client.execute(XMLRPC119Handler.class.getName()
+ ".getString", new Object[]{new Integer(i)});
assertEquals(i*1024, s.length());
System.out.println(i + ": " + (System.currentTimeMillis() - now));
}
}
In all cases the test takes less than 150 ms, even for a 90k string.
> 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
