High usages with new builder
Hi,
I was trying to move two of my services to the new builder and that was a wild ride, follow me.
- I toggled the "new builder" option + new runtime "v2".
- I deployed, and went on with my life.
- Checked ~20 mins later and all the usage went to the roof.
The two services I toggled the new builder are cron/worker services, the memory usage has been around ~150/200MB for many months. After deploying with the new builder that what's I got (first image), that doesn't look normal. To comparison, second image is the "normal" usage before trying the new builder.
I, of course, disabled the new builder again, and usage went back to normal. I did keep runtime "v2" on because that part is good.
Is it a display/metrics issue, or am I doing something wrong to get that crazy usage?
I'm deploying docker images, with node-alpine base.
34849d22-d685-4e73-8858-fbd4fe42ea65
Solution:Jump to solution
hey, @alex and @jeremy - a fix was merged for this, let me know if you experience these issues again!
21 Replies
Project ID:
34849d22-d685-4e73-8858-fbd4fe42ea65very strange
@Brody @Adam yoink
seems related to #Impossible reporting statisttics on railway project
When I have time I'm going to test this with the old builder and see if my reporting reduces
okay thank you, I'll bring this up to the team monday
!t
New reply sent from Help Station thread:
This thread has been escalated to the Railway team.You're seeing this because this thread has been automatically linked to the Help Station thread. New reply sent from Help Station thread:
Hey there,So a few things:1. Builds don't count towards your usage on the platform.2. The result of the image on the new runtime results may or may not be respecting cgroup rules. Raised this to our build engineer to run an investigation.Will keep you in the loop, keep in mind Christian is going on call, so you will see him engage in the thread as time goes on.You're seeing this because this thread has been automatically linked to the Help Station thread.
ko
Any updates on this?
Solution
hey, @alex and @jeremy - a fix was merged for this, let me know if you experience these issues again!
@flatypus
that's so real
my app should not be using 32GB of ram
it does like nothing
lol
@alex seems like for me the memory is garbage collected by python, but memory isn't freed to the OS (python apparently operates on some abstraction layer, i'm not quite confident here)
so idle is supposed to be 145MB, that can't be changed
hey at least it's not 20GB like yesterday
ima try dockerizing this tmr