Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

Okay, testing with .js is cruising along. It's consuming up to 3 GB of memory at peak times, but that's a huge improvement over Hollo with , which was consuming over 8 GB of memory at peak times.

So, yes, starting with Hollo 0.4.0, we'll use Node.js instead of Bun!

Memory usage chart for the hollo.social server. You can see that before December 18th, the point at which we switched to Node.js, the memory usage fluctuated between 1 GB and 8 GB, but since then, it's been mostly stable around 1 GB. It did spike to 3 GB at peak times, but only briefly during the entire test period.
ALT text detailsMemory usage chart for the hollo.social server. You can see that before December 18th, the point at which we switched to Node.js, the memory usage fluctuated between 1 GB and 8 GB, but since then, it's been mostly stable around 1 GB. It did spike to 3 GB at peak times, but only briefly during the entire test period.
Olivier Forget's avatar
Olivier Forget

@teleclimber@social.tchncs.de · Reply to Hollo :hollo:'s post

@hollo what kind of activity are we talking about here? How much posting, how many followers, etc... Because 3 Gigs of memory is still quite a bit, no? Is that just the reality for activity pub based systems?

Emelia 👸🏻's avatar
Emelia 👸🏻

@thisismissem@hachyderm.io · Reply to Hollo :hollo:'s post

@hollo I could be curious to see this compared to deno too?