szurubooru/server/docker-start.sh

#!/usr/bin/dumb-init /bin/sh
set -e
cd /opt/app

alembic upgrade head

echo "Starting szurubooru API on port ${PORT} - Running on ${THREADS} threads"
exec waitress-serve-3 --port ${PORT} --threads ${THREADS} szurubooru.facade:app
server/docker: use Alpine-based image for space savings 2019-09-30 00:39:16 +02:00			`#!/usr/bin/dumb-init /bin/sh`
server/docker: improved Dockerfile 2019-09-28 05:15:34 +02:00			`set -e`
			`cd /opt/app`

			`alembic upgrade head`

Make waitress thread count configurable. This should fix most scaling problems without needing to start more server instances. By default, waitress maintains at most 4 threads. This works fine if the database is small (sub 100k posts) but causes a large Task queue depth to occur if the database is larger. Letting users increase the amount of threads means that one server instance is able to handle more requests without locking up the rest of the site. This adds a new environment variable to .env, THREADS, which can be used to configure the amount of threads to start and is by default set to 4 (the default amount used by waitress). 2022-02-12 22:16:13 +01:00			`echo "Starting szurubooru API on port ${PORT} - Running on ${THREADS} threads"`
			`exec waitress-serve-3 --port ${PORT} --threads ${THREADS} szurubooru.facade:app`