Very poor performance

[igor47]

Tandoor Version

abf8f791360b2bc4a5c7d011877668679bcbb3f2

Setup

Docker / Docker-Compose

Reverse Proxy

Traefik

Other

No response

Bug description

seeing very poor performance with not too many recipes. for instance, here's one example of a search page. my instance has maybe 7 to 9 recipes right now and this request took 15 seconds:

i was originally just serving static files with gunicorn, but moved it to nginx with no improvement in performance. i also tried increasing the number of gunicorn workers.

another example with a best-case scenario of around 2 seconds, which is still very slow and laggy:

i can repro by just shift-reloading from /search/

Relevant logs

i don't see anything specific in the logs. there's occasional timeouts, but them seem unrelated to slow requests. for example:

tandoor.purr-1  | [2023-12-23 01:39:08 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:67)
tandoor.purr-1  | [2023-12-23 01:39:09 +0000] [1] [WARNING] Worker with pid 67 was terminated due to signal 9

[LeGmask]

I'm facing the same issue, and the app only has two recipes

[smilerz]

Try rebuilding the recipe index in Admin (under the recipe objects)

[Hoffelhas]

Try rebuilding the recipe index in Admin (under the recipe objects)

Couldn't find this, how do you do this exactly?

[smilerz]

/admin/cookbook/recipe/ --> rebuild index (make sure you select all recipes)

[Hoffelhas]

Ah there it is! Thank you. Was able to re-index 'recipe', and also delete any unused values at 'step'.

After doing this the Recipes page doesn't seem to load any faster. Similarly to LeGmask, I only have two recipes yet, but it already takes ~5 seconds to load the page.

[smilerz]

these are typically indicative of low memory conditions. Are you running this on a low powered device and with Postgres on the same system?

tandoor.purr-1  | [2023-12-23 01:39:08 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:67)
tandoor.purr-1  | [2023-12-23 01:39:09 +0000] [1] [WARNING] Worker with pid 67 was terminated due to signal 9

[igor47]

these are typically indicative of low memory conditions. Are you running this on a low powered device and with Postgres on the same system?

for me, no. i am running postgres on the same system, but the machine has 16G ram with around 9GB free, and an 8-core intel i7 generally running > 90% idle

[smilerz]

these are typically indicative of low memory conditions. Are you running this on a low powered device and with Postgres on the same system?

for me, no. i am running postgres on the same system, but the machine has 16G ram with around 9GB free, and an 8-core intel i7 generally running > 90% idle

Your django instance running out of memory - you'll need to troubleshoot why that is.