High Memory Use with Baserow Template
rthidden
PROOP

a month ago

How can I reduce the Memory Use & Cost of the Baserow?

I have an automation adding records ~5 times a week. They are real estate listings usually no more than 10 homes a day. Each record is text only so should be small size.

I am not sure what other information may be needed to help diagnose and come up with a solution. Let me know if more info is needed.

Thanks,
Ryan


Attachments

image.png
image.png
image.png
Solved$20 Bounty

Pinned Solution

ilyassbreth
FREE

a month ago

so i did some analysis on this , your memory is eating 96% of costs ($26 out of $27). you're running around 2.5gb constantly which seems high for just adding 10 records 5x/week

from what i found in the baserow docs, you might be able to reduce memory by trying these env vars on your baserow service:

  • BASEROW_RUN_MINIMAL=yes

  • BASEROW_AMOUNT_OF_WORKERS=1 (handles background tasks, defaults to number of cpu cores)

  • BASEROW_AMOUNT_OF_GUNICORN_WORKERS=1 (handles api requests, defaults to 3, each uses 100-200mb ram)

also check if your railway template deployed multiple services (postgres, baserow, redis). if you see separate cards for each in your project, they're all using memory individually

go to your baserow service settings → try adding those variables above and redeploy. should help reduce memory usage

reducing workers could potentially get you down to the 1gb range which would cut costs to around $10/month

i hope this help you slightly_smiling_face emoji

2 Replies

ilyassbreth
FREE

a month ago

so i did some analysis on this , your memory is eating 96% of costs ($26 out of $27). you're running around 2.5gb constantly which seems high for just adding 10 records 5x/week

from what i found in the baserow docs, you might be able to reduce memory by trying these env vars on your baserow service:

  • BASEROW_RUN_MINIMAL=yes

  • BASEROW_AMOUNT_OF_WORKERS=1 (handles background tasks, defaults to number of cpu cores)

  • BASEROW_AMOUNT_OF_GUNICORN_WORKERS=1 (handles api requests, defaults to 3, each uses 100-200mb ram)

also check if your railway template deployed multiple services (postgres, baserow, redis). if you see separate cards for each in your project, they're all using memory individually

go to your baserow service settings → try adding those variables above and redeploy. should help reduce memory usage

reducing workers could potentially get you down to the 1gb range which would cut costs to around $10/month

i hope this help you slightly_smiling_face emoji

ilyassbreth

so i did some analysis on this , your memory is eating 96% of costs ($26 out of $27). you're running around 2.5gb constantly which seems high for just adding 10 records 5x/weekfrom what i found in the baserow docs, you might be able to reduce memory by trying these env vars on your baserow service:BASEROW_RUN_MINIMAL=yesBASEROW_AMOUNT_OF_WORKERS=1 (handles background tasks, defaults to number of cpu cores)BASEROW_AMOUNT_OF_GUNICORN_WORKERS=1 (handles api requests, defaults to 3, each uses 100-200mb ram)also check if your railway template deployed multiple services (postgres, baserow, redis). if you see separate cards for each in your project, they're all using memory individuallygo to your baserow service settings → try adding those variables above and redeploy. should help reduce memory usagereducing workers could potentially get you down to the 1gb range which would cut costs to around $10/monthi hope this help you

rthidden
PROOP

a month ago

Thanks! I made these changes yesterday and the RAM usage dropped to 1GB.

Now let's see if there are any performance issues. slightly_smiling_face emoji If there are I will report back, so far so good.

Thanks again.

+11

Status changed to Solved noahd • about 1 month ago

Loading...