Open foursixnine opened 3 months ago
Description of problem
Running with podman-compose (python 3.11, and 3.12) results in few errors, resulting in high load on wsgi and decreased peformance
Can you be more specific here. How do you know what it is the wsgi process that spikes the CPU load?
I tried a podman-compose up
with podman-5.1.2-1.fc40.x86_64, podman-compose-1.2.0-1.fc40.noarch, Python 3.12.4
and htop barely registers the containers.
Is this before initial_setup
or after ?
Did you pull all images from docker.io or from other docker registries ?
as soon as I restart the containers, and after navigating to any of the pages:
Jul 29 21:35:36 istabl-antar02 kiwi_web[3053]: 127.0.0.1 - - [29/Jul/2024:21:35:36 +0000] "GET /accounts/login/ HTTP/1.1" 200 15292 "healthcheck" "curl/7.76.1" "-" Jul 29 21:35:52 istabl-antar02 kiwi_web[3053]: [redacted] - - [29/Jul/2024:21:35:52 +0000] "MGLNDD_[redacted]_443" 400 157 "-" "-" "-" Jul 29 21:36:04 istabl-antar02 systemd[1376]: podman-compose@KIWI.service: State 'stop-sigterm' timed out. Killing. Jul 29 21:36:04 istabl-antar02 systemd[1376]: podman-compose@KIWI.service: Killing process 3053 (conmon) with signal SIGKILL. Jul 29 21:36:04 istabl-antar02 systemd[1376]: podman-compose@KIWI.service: Killing process 3148 (conmon) with signal SIGKILL. Jul 29 21:36:04 istabl-antar02 systemd[1376]: podman-compose@KIWI.service: Failed with result 'exit-code'.
1. vm has 2 cores & 2 gb of ram
Is there any difference if you bump ram and CPU? I would suspect that RAM is more important b/c it is I/O driven application but still 2 GB should be enough for a single instance.
464fb643184e [redacted-host] - - [29/Jul/2024:21:35:52 +0000] "MGLNDD_[redacted]_443" 400 157 "-" "-" "-"
Only this line is unfamiliar. What is this ? Is it some sort of external probe ?
This is the journal log:
Jul 29 20:46:21 istabl-antar02 systemd[1339]: Starting KIWI rootless pod (podman-compose)... Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: Traceback (most recent call last): Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: File "/usr/bin/podman-compose-3.12", line 33, in <module> Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: sys.exit(load_entry_point('podman-compose==1.2.0', 'console_scripts', 'podman-compose')()) Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: File "/usr/lib/python3.12/site-packages/podman_compose.py", line 3503, in main Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: asyncio.run(async_main()) Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: File "/usr/lib64/python3.12/asyncio/runners.py", line 194, in run Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: return runner.run(main) Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: ^^^^^^^^^^^^^^^^ Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: File "/usr/lib64/python3.12/asyncio/runners.py", line 118, in run Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: return self._loop.run_until_complete(task) Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: File "/usr/lib64/python3.12/asyncio/base_events.py", line 687, in run_until_complete Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: return future.result() Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: ^^^^^^^^^^^^^^^ Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: File "/usr/lib/python3.12/site-packages/podman_compose.py", line 3499, in async_main Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: await podman_compose.run() Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: File "/usr/lib/python3.12/site-packages/podman_compose.py", line 1740, in run Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: self._parse_compose_file() Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: File "/usr/lib/python3.12/site-packages/podman_compose.py", line 1882, in _parse_compose_file Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: raise RuntimeError(f"Project name [{dir_basename}] normalized to empty") Jul 29 20:46:21 istabl-antar02 podman-compose-3.12[2474]: RuntimeError: Project name [kiwitcms] normalized to empty Jul 29 20:46:21 istabl-antar02 podman[2482]: 2024-07-29 20:46:21.330735204 +0000 UTC m=+0.040582802 pod start 4bc1bf499e3ef68d85ee29e596d4a5050729cb471f3f39dcbb70547b1550fe87 (image= , name=pod_KIWI)
I am not seeing anything like this in th ejournal log from podman. Could it be that you are using a buggy version ?
Description of problem
Running with podman-compose (python 3.11, and 3.12) results in few errors, resulting in high load on wsgi and decreased peformance
as soon as I restart the containers, and after navigating to any of the pages:
the result of the podman-compose logs is:
Version or commit hash (if applicable)
using docker.io/kiwitcms/kiwi:latest
Steps to Reproduce
followed: https://kiwitcms.readthedocs.io/en/latest/installing_docker.html
Actual results
System is very slow, wsgi has high load
Expected results
Additional info (Python traceback, logs, etc.)
This is the journal log: