Are you requesting the results in the same order in both cases? (I don't know what the arguments in your code represent)
If you retrieve oldest to youngest some delay is expected as then first all interesting revisions are fetched (youngest to oldest) and then results+detailed are spooled back the other way. The normal svn invocation you compare to is the most efficient one... Bert -----Original Message----- From: "Marc Strapetz" <marc.strap...@syntevo.com> Sent: 13-3-2015 20:35 To: "dev@subversion.apache.org" <dev@subversion.apache.org> Subject: 1.9.x JavaHL: long initial delay when performing a log I'm experiencing a strange initial delay when performing a log using JavaHL. svn log http://svn.apache.org/repos/asf/subversion/branches/1.8.x shows first results after 2-3 seconds, while following code snippet takes at least 20 seconds (sometimes significantly more, might depend on the server's load): ISVNRemote session = factory.openRemoteSession("http://svn.apache.org/repos/asf";); List<String> paths = Collections.singletonList("subversion/branches/1.8.x"); session.getLog(paths, Revision.SVN_INVALID_REVNUM, 0, 0, false, false, false, null, new LogMessageCallback() { public void singleMessage(Set<ChangePath> changedPaths, long revision, Map<String, byte[]> revprops, boolean hasChildren) { System.out.println("DATA"); } }); Once the log responds, a bunch of revisions are reported, so it seems that there is some kind of caching of log records. I've tested with latest 1.9.x sources on Windows but have seen the same behavior with javahl-1.8-extensions branch on Linux, too. -Marc
