Radicale quite slow after fresh installation with just one item in the calendar #1466
Assignees
Labels
Comments
Skaronator
added a commit
to Skaronator/homelab
that referenced
this issue
Apr 6, 2024
|
Probably same issue reported in #1282 |
|
could you please use following branch for testing, I've added some profiling output here...will extend on demand:'https://github.com/pbiering/Radicale/tree/add-profiling Enable it using Example output: Please post your's. |
|
Thanks for the swift response! Sadly, I'm unable to build the container image. I tried building the Dockerfile.dev image, but it seems not to include the latest changes. When searching for the code within the image I cannot find anything relevant. I'm not that familiar with the python/pip install stage. From the container image it should be somewhere in /app/ but I can don't see anything: /app $ ls -lsah /app/*
0 lrwxrwxrwx 1 radicale radicale 3 Apr 7 08:28 /app/lib64 -> lib
4.0K -rw-r--r-- 1 radicale radicale 165 Apr 7 08:28 /app/pyvenv.cfg
/app/bin:
total 56K
4.0K drwxr-xr-x 2 radicale radicale 4.0K Apr 7 08:28 .
4.0K drwxr-xr-x 1 root root 4.0K Apr 7 08:28 ..
12.0K -rw-r--r-- 1 radicale radicale 8.8K Apr 7 08:28 Activate.ps1
4.0K -rw-r--r-- 1 radicale radicale 2.0K Apr 7 08:28 activate
4.0K -rw-r--r-- 1 radicale radicale 903 Apr 7 08:28 activate.csh
4.0K -rw-r--r-- 1 radicale radicale 2.1K Apr 7 08:28 activate.fish
4.0K -rwxr-xr-x 1 radicale radicale 220 Apr 7 08:28 change_tz
4.0K -rwxr-xr-x 1 radicale radicale 219 Apr 7 08:28 ics_diff
4.0K -rwxr-xr-x 1 radicale radicale 225 Apr 7 08:28 pip
4.0K -rwxr-xr-x 1 radicale radicale 225 Apr 7 08:28 pip3
4.0K -rwxr-xr-x 1 radicale radicale 225 Apr 7 08:28 pip3.12
0 lrwxrwxrwx 1 radicale radicale 21 Apr 7 08:28 python -> /usr/local/bin/python
0 lrwxrwxrwx 1 radicale radicale 6 Apr 7 08:28 python3 -> python
0 lrwxrwxrwx 1 radicale radicale 6 Apr 7 08:28 python3.12 -> python
4.0K -rwxr-xr-x 1 radicale radicale 218 Apr 7 08:28 radicale
/app/include:
total 12K
4.0K drwxr-xr-x 3 radicale radicale 4.0K Apr 7 08:28 .
4.0K drwxr-xr-x 1 root root 4.0K Apr 7 08:28 ..
4.0K drwxr-xr-x 2 radicale radicale 4.0K Apr 7 08:28 python3.12
/app/lib:
total 12K
4.0K drwxr-xr-x 3 radicale radicale 4.0K Apr 7 08:28 .
4.0K drwxr-xr-x 1 root root 4.0K Apr 7 08:28 ..
4.0K drwxr-xr-x 3 radicale radicale 4.0K Apr 7 08:28 python3.12The only file that is called radicale contains only these few lines: /app $ cat /app/bin/radicale
#!/app/venv/bin/python
# -*- coding: utf-8 -*-
import re
import sys
from radicale.__main__ import run
if __name__ == '__main__':
sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])
sys.exit(run())My image is available here: |
|
Sorry, can't support such deployments for troubleshooting at the moment, try to apply the changes manually to the related files: |
|
I'll try to build a working image on the weekend. |
|
Hi, I was able to get the image working. It looks like the issue fixed itself?! I guess it's due to the newer release. Here is the log with profiling and the newer version: radicale [2024-05-19 17:24:29 +0200] [1/Thread-56 (process_request_thread)] [INFO] Successful login: 'niklas'
radicale [2024-05-19 17:24:29 +0200] [1/Thread-56 (process_request_thread)] [INFO] profiling/PROPFIND/_xml_propfind: begin
radicale [2024-05-19 17:24:29 +0200] [1/Thread-56 (process_request_thread)] [INFO] profiling/PROPFIND/_collect_allowed_items: begin
radicale [2024-05-19 17:24:29 +0200] [1/Thread-56 (process_request_thread)] [INFO] profiling/PROPFIND/_collect_allowed_items: end 1 items in 0.000 seconds
radicale [2024-05-19 17:24:29 +0200] [1/Thread-56 (process_request_thread)] [INFO] profiling/PROPFIND/_xml_propfind: end after 0.000 seconds
radicale [2024-05-19 17:24:29 +0200] [1/Thread-56 (process_request_thread)] [INFO] PROPFIND response status for '/niklas' with depth '0' in 0.096 seconds: 207 Multi-Status
radicale [2024-05-19 17:24:35 +0200] [1/Thread-58 (process_request_thread)] [INFO] GET request for '/' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:35 +0200] [1/Thread-58 (process_request_thread)] [INFO] GET response status for '/' in 0.000 seconds: 302 Found
radicale [2024-05-19 17:24:35 +0200] [1/Thread-59 (process_request_thread)] [INFO] GET request for '/' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:35 +0200] [1/Thread-59 (process_request_thread)] [INFO] GET response status for '/' in 0.000 seconds: 302 Found
radicale [2024-05-19 17:24:35 +0200] [1/Thread-60 (process_request_thread)] [INFO] GET request for '/.web' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:35 +0200] [1/Thread-60 (process_request_thread)] [INFO] GET response status for '/.web' in 0.000 seconds: 302 Found
radicale [2024-05-19 17:24:35 +0200] [1/Thread-61 (process_request_thread)] [INFO] GET request for '/.web' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:35 +0200] [1/Thread-61 (process_request_thread)] [INFO] GET response status for '/.web' in 0.000 seconds: 302 Found
radicale [2024-05-19 17:24:35 +0200] [1/Thread-62 (process_request_thread)] [INFO] GET request for '/.web/' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:35 +0200] [1/Thread-63 (process_request_thread)] [INFO] GET request for '/.web/' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:35 +0200] [1/Thread-62 (process_request_thread)] [INFO] GET response status for '/.web/' in 0.001 seconds: 200 OK
radicale [2024-05-19 17:24:35 +0200] [1/Thread-63 (process_request_thread)] [INFO] GET response status for '/.web/' in 0.000 seconds: 200 OK
radicale [2024-05-19 17:24:45 +0200] [1/Thread-64 (process_request_thread)] [INFO] GET request for '/' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:45 +0200] [1/Thread-64 (process_request_thread)] [INFO] GET response status for '/' in 0.000 seconds: 302 Found
radicale [2024-05-19 17:24:45 +0200] [1/Thread-65 (process_request_thread)] [INFO] GET request for '/' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:45 +0200] [1/Thread-65 (process_request_thread)] [INFO] GET response status for '/' in 0.000 seconds: 302 Found
radicale [2024-05-19 17:24:45 +0200] [1/Thread-66 (process_request_thread)] [INFO] GET request for '/.web' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:45 +0200] [1/Thread-66 (process_request_thread)] [INFO] GET response status for '/.web' in 0.000 seconds: 302 Found
radicale [2024-05-19 17:24:45 +0200] [1/Thread-67 (process_request_thread)] [INFO] GET request for '/.web' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:45 +0200] [1/Thread-67 (process_request_thread)] [INFO] GET response status for '/.web' in 0.000 seconds: 302 Found
radicale [2024-05-19 17:24:45 +0200] [1/Thread-68 (process_request_thread)] [INFO] GET request for '/.web/' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:45 +0200] [1/Thread-69 (process_request_thread)] [INFO] GET request for '/.web/' received from 10.244.1.1 using 'kube-probe/1.30'
radicale [2024-05-19 17:24:45 +0200] [1/Thread-68 (process_request_thread)] [INFO] GET response status for '/.web/' in 0.001 seconds: 200 OK
radicale [2024-05-19 17:24:45 +0200] [1/Thread-69 (process_request_thread)] [INFO] GET response status for '/.web/' in 0.000 seconds: 200 OKMy Dockerfile was pretty straightforward in the end: FROM tomsquest/docker-radicale
RUN /venv/bin/pip install --no-cache-dir git+https://github.com/pbiering/Radicale.git@add-profiling
|
|
I just retested using the older version and the issue is gone as well?! Really weird. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I just deployed Radicale 3.9.1 using the tomsquest/docker-radicale Container Image.
I noticed right from the beginning that Radicale is really slow. Looking at the logs confirms it. Every data request takes over 2 seconds.
I don't think it's a hardware issue for me. The machine has 128 GB RAM, 16 Core CPU, Idles at 0.63 (less than one core) and the storage is blazing fast NVMe in a ZFS Mirror.
Log
Config
The text was updated successfully, but these errors were encountered: