You are viewing a single comment's thread.

view the rest of the comments →

caprep ago

What is the biggest cost right now? Bandwidth? Memory? CPU? Disk?

If we knew the biggest issue we could focus on that first.

Is Putt running the same sized instances all the time, or scaling up / down instances as traffic demands it?

Suggestions:

Bandwidth - Make all images WebP and save ~25% of image bandwidth right away.

Bandwidth idea 2 - Minify the HTML. There are a lot of long class names in the code and extraneous spaces. I'm sure we could easily get a 20% bandwidth savings from the main HTML.

Disk - Take old posts, put them into a torrent and delete them from voat. If people want them they can host them.

CPU - Most of the visitors probably aren't logged in. Why not compile a static HTML page every 30 seconds and save it to disk. When a non-logged in visitor views the main page give them the stored one. Same with comments on popular articles. The page doesn't need to be up to the second

Memory - Most all of the suggestions above should help, especially the pre-compute option.

There are a number of quick things we can do to relive the pressure, we just need to know where to aim our autism.

WhiteRonin ago

Yep, yep and more yeps ...