#Memory usage

64 messages · Page 1 of 1 (latest)

sly mango
#

I noticed the usage page and the metrics page seem to be showing different numbers. On the metrics I don't see any points today where my memory was around 2GB but I do see that in the usage page.

Could this be because at some points 2 instances were running because of the deploy process?

north bladeBOT
#

Project ID: N/A

sly mango
#

a1c26f65-931b-4555-89d8-3808152699c9

sly mango
#

Bumping this

summer echo
#

#1084162901494993006

#

^ may be related

sly mango
#

yeah seems likely. hoping its a display issue from multiple deploys.

north bladeBOT
#

Flagging this thread. A team member will be with you shortly.

glass heron
#

Going to look into this tomorrow

sly mango
#

In saying that there's a disconnect somewhere as the top numbers for both graphs are different. 🤔

image.png
glass heron
#

Oh wait, that’s on the usage page right?

sly mango
#

first set is project, second is usage page.

glass heron
#

Do you have other stuff in the project, like db etc.?

sly mango
#

nope

glass heron
#

Mmm weird

sly mango
glass heron
#

I’ll poke into it and keep you posted

sly mango
#

All good, im almost certain its a graphical thing as my bills arent randomly shooting up

glass heron
#

so, I think this is graphical confusion 🙂

they represent different time periods, so that 2.85GB you see on the usage page is likely from a different time range than your project's metrics

#

I don't see anything off, but if your bill shoots up unexpectedly, can you ping me here?

sly mango
summer echo
frosty compass
#

yeah it's just a display bug, I've seen this exact same thing with other people besides fragly and I have never heard of anyone getting over charged because of it, so there's nothing to worry about, just rely on your service metrics

sly mango
#

okay it seems to be even worse when you've just made a fresh project and then do a few deploys. it should show around 150MB - 200MB not 42GB lol

image.png
frosty compass
#

holy shit

#

is 2.5 for the cpu even correct?

sly mango
#

i dont think so.

frosty compass
#

this is by far the worst I've seen it, previous was 12gb

sly mango
#

314f0687-1c78-47f8-88c0-61e20cf0b9b6

frosty compass
#

congratulations on the new record

sly mango
sly mango
#

it happened as soon as i did the first few successive commits.

#

3 containers were running at the same time at one point

#

thats when it started jumping

#

actual usage lol

image.png
#

thats the last two deploys.

#

nowhere near the 42GB 😅

frosty compass
#

this bug has been going on for a while, its harmless but very annoying

sly mango
#

It's getting worse 👀

image.png
summer echo
#

100GB ram usage speedrun?

sly mango
#

guess i just wont use the estimate panel 😢

frosty compass
#

it does still say 2$ if the estimation was based off of those metrics you would be somewhere around 500$

sly mango
#

|| its honestly not a worry i just find this funny as ||

#

its still going up.. this isnt how it usually behaves.

#

normally it settles. now it's gone up another gig again and im not even deploying

frosty compass
#

speed run lfg

sly mango
#

i mean thats pretty cheap. nice sale you guys have.. $2 for 55GB chefkiss

frosty compass
#

can't beat those prices

sly mango
#

curious, would it be the RSS in node that's the actual memory usage as per billing?

#

trying to work out the real memory usage now.

glass heron
#

heya can you share the project ID for this?

#

great reproduction case 😄

glass heron
sly mango
#

Another instance of this UI bug

image.png image.png
dusty matrix
#

@glass heron i have the same issue, it shows that i am using memory sometimes and vCPU sometimes and getting billed for it while i am using 40-100 mb ram and 0-1 percent cpu so its definitely glitched

#

(got real data from metrics page)

#

oh wait pinging is prohibited, i am so sorry

dusty matrix