Gerhard Lazu

So you can see how many times this has happened.

And that's like an important metric that if we look at, we can see we had too many of these events, right?

Like many objects were being nuked from memory to make room for new objects, but sometimes they wouldn't fit.

So how badly did it nuke?

Because we can measure this.

We can look at this.

And this is what it looks like from a memory perspective.

So you can see that the instance was running about maybe four gigs of memory.

And then we had a massive spike within minutes, like one or two minutes, to 16 gigabytes.

So that's a lot of data that had to be fit in memory.

And you can already see where this is going.

Scrapers and bots and LLMs.

And we have so many things happening.

And then you can see the memory went up

the thread was killed, the child was killed, like the varnish once the memory came down again, and then it went up again.

So the graph that we see here, we can see the first spike, just like maybe a minute apart, the second spike, another crash, it took a little while for it to restore, we're talking maybe 10 seconds, and then we stabilized around 10 gigabytes.

From a CPU perspective, we got like 100% CPU utilization when this happens.

Like everything is full on, everything, like the instance is really struggling to allocate and deallocate and free up memory.

And more importantly, we have a lot of traffic

flowing through so how much 2.29 gigabyte gigabits specifically 2.29 gigabits per second per second exactly and these happen so quickly have like a a huge rush of traffic coming in and then nothing