shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

264
active users

#cache

0 posts0 participants0 posts today

I got some feedback about how slow my #blog is to load. I decided to try my hand at setting up an #nginx #cache so that the requests can be satisfied by the cache instead of being generated by the blog software itself.

Just doing a few quick tests myself, it seems the like responses come a bit quicker, but I still think some of the delay is just due to the garbage residential Spectrum service.

If anyone would like to poke at my blog and share any observations on load time and potential cache performance, that'd be cool. :-)
#homelab #selfhost #selfhosting

After I published a recent article where I showed how to mitigate an accidental DDoS after enabling ActivityPub for WordPress with the Surge plugin, I found an optimization for improved cache handling. Out of the box, there’s a problem with the default configuration since Surge ignores the Accept header.

[…]

epiph.yt/en/blog/2025/optimize

Epiphyt · Surge-Konfiguration für ActivityPub optimieren | EpiphytDas Plugin Surge ignoriert den für ActivityPub wichtigen Accept-Header. Durch eine clevere Lösung kannst du dafür eine eigene Cache-Version bereitstellen.

👑 Cache is King: Smart Page Eviction with eBPF

arxiv.org/abs/2502.02750

arXiv.orgCache is King: Smart Page Eviction with eBPFThe page cache is a central part of an OS. It reduces repeated accesses to storage by deciding which pages to retain in memory. As a result, the page cache has a significant impact on the performance of many applications. However, its one-size-fits-all eviction policy performs poorly in many workloads. While the systems community has experimented with a plethora of new and adaptive eviction policies in non-OS settings (e.g., key-value stores, CDNs), it is very difficult to implement such policies in the page cache, due to the complexity of modifying kernel code. To address these shortcomings, we design a novel eBPF-based framework for the Linux page cache, called $\texttt{cachebpf}$, that allows developers to customize the page cache without modifying the kernel. $\texttt{cachebpf}$ enables applications to customize the page cache policy for their specific needs, while also ensuring that different applications' policies do not interfere with each other and preserving the page cache's ability to share memory across different processes. We demonstrate the flexibility of $\texttt{cachebpf}$'s interface by using it to implement several eviction policies. Our evaluation shows that it is indeed beneficial for applications to customize the page cache to match their workloads' unique properties, and that they can achieve up to 70% higher throughput and 58% lower tail latency.
#linux#kernel#cache

For the love of god if you're trying to convince your employer or an organization to "come over" to the #Fediverse, do NOT under any circumstances suggest that they set up a #Mastodon #instance!

Mastodon is the ONLY Fediverse platform that ...
by default ... forces #server #admins to #cache, #copy, and #proxy all #media that passes through its server. This means that not only are server admins paying to host the media their users #upload, but they have to pay to host the media everyone else on the fucking fediverse uploads as well.

Other platforms offer this feature, but
Mastodon is the only one that has this turned on by default.

This results in Mastodon server admins having to shell out thousands of dollars each month in
#S3 hosting costs for no reason whatsoever.

There are much better alternative instance platforms than Mastodon.

Replied in thread

@marcy I'd say that unless you're constantly doing a lot of IOPS-heavy tasks, you won't even notice the difference between a BX500 120G SSD and the fastest Crucial NVMe - SSD.

  • I mean, if you're constantly building big software projects (like @fuchsiii constantly compiling #wine) you won't notice much of a difference.

Only once you do a lot of writing of big files will you notice things like DRAM-#Cache and Interface speeds.

  • Just because benchmarks make a number go up doesn't mean that's a good decision. Espechally on mobile setups you may want to have a slower but more power-efficient drive instead of the fastest you can put in...