I re-verified the behavior on a third (fast) machine with SDD and the result as still bad with an average of 900-1000ms per request.

Andreas


On 4 Jan 2019, at 12:13, Andreas Jung wrote:

The original tests below have been made on a virtualized machine with 8 cores, 64 GB RAM.
My first idea was about the shared storage, filesystem. So I tried with the same dataset on my local
machine and the result is even worse: 1700ms for PROPFIND on the root of the database containing only
on object in the root:

12:10:26.294 127.0.0.1:53202 admin REQUEST OPTIMIZE ALL 2.37 ms
12:10:41.396 127.0.0.1:53202 admin OK Database 'onkopedia' was optimized in 15102.34 ms. 15102.77 ms
12:10:42.646 127.0.0.1:35556 admin REQUEST [PROPFIND] http://localhost:8984/webdav/onkopedia/
12:10:44.346 127.0.0.1:35556 admin 200 1700.02 ms

Andreas

On 4 Jan 2019, at 11:37, Andreas Jung wrote:

I have an optimized database with 25K objects, 8 GB of data running on 9.1.1.

WebDAV operations are very slow (client running and connecting locally).
The response times are by a magnitude slower compared to exist-db.
Is there some something missing in the configuration in order to speed this up significantly?

Andreas

11:28:16.899 127.0.0.1:45822 admin OK Database 'onkopedia' was optimized in 29379.65 ms. 29380.24 ms
11:28:25.382 0:0:0:0:0:0:0:1:34258 admin 200 694.07 ms
11:28:26.065 0:0:0:0:0:0:0:1:34260 admin 200 675.31 ms
11:28:26.770 0:0:0:0:0:0:0:1:34262 admin 200 691.53 ms
11:28:29.231 0:0:0:0:0:0:0:1:34264 admin 200 2444.93 ms
11:28:29.856 0:0:0:0:0:0:0:1:34266 admin 200 616.41 ms
11:28:32.310 0:0:0:0:0:0:0:1:34268 admin 200 2445.99 ms
11:28:33.083 0:0:0:0:0:0:0:1:34270 admin 200 766.14 ms
11:28:33.719 0:0:0:0:0:0:0:1:34272 admin 200 615.38 ms