You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running tuwunel inside an unprivileged LXC on a Proxmox host. Tuwunel runs as binary on a fedora guest. Since I added some users, I often appear to be suffering write stalling. The write ahead log grows, sometimes it jumps from 1 to 20 or 40 or even 60. If this happens, the app does not crash, but I notice no messages go in or out. I then have to restart tuwunel.
tuwunel has exclusive access to two cores of an i5-12400, 8GB RAM and runs on an NVME. I have only three active users. So that hardware should be fine?
Are the database or other settings, which can ensure reliable functionality in shared environments, where no process of tuwunel has exclusive access to I/O or CPU cycles?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm running tuwunel inside an unprivileged LXC on a Proxmox host. Tuwunel runs as binary on a fedora guest. Since I added some users, I often appear to be suffering write stalling. The write ahead log grows, sometimes it jumps from 1 to 20 or 40 or even 60. If this happens, the app does not crash, but I notice no messages go in or out. I then have to restart tuwunel.
tuwunel has exclusive access to two cores of an i5-12400, 8GB RAM and runs on an NVME. I have only three active users. So that hardware should be fine?
Are the database or other settings, which can ensure reliable functionality in shared environments, where no process of tuwunel has exclusive access to I/O or CPU cycles?
Beta Was this translation helpful? Give feedback.
All reactions