Peter Bieringer

also check for listen daemon and SElinux settings, can be that Apache is by default blocked to connect further on.

There are HTTP client implementations out which first send a request without username:password and then server respond with `401` and provides the basic realm and client can then lookup username:password...

can you check your system regarding - consumed memory of the process, e.g. `ps -F -C radicale` - system swap state, e.g. `free` - current load on the system `cat...

Looks like your system has an IO and/or CPU issue, the "idle" column turns from usually 99 down to 0 while the "wait" column turns up from 0 to nearly...

did this problem disappear since last report?

> which seems excessive when the whole collection is a bit over 1GB Your collection has a size of over 1 GByte on disk? That's huge and potentially an explanation...

What filesystem are you using? If "ext*" and there are a huge amount of files in one single directory this can also be a reason. In this case try to...

Hmm, the sync token directory has a large size. You can stop "radicale", remove directory ".Radicale.cache" complete, create it on `/dev/shm/collection-root/$COLLECTION/.Radicale.cache` and create a symlink towards in the original collection...

> bottleneck was always the filesystem which filesystem type was in use? > especially when it lists the files in directories This can be related to file system type and...

Can you provide detailed logs from Apache and Radicale?