Show newer

with more shiny graphs at the bottom of stats.pixie.town/d/rPBvoh6Gk/s

and a slowly increasing cache hit ratio (its all-time so will take a while) just went from 29.4 to 29.5%

Show thread

this makes *such* a difference, like rn there's 46 entries 5.26 MB/200 MB (just restarted), so it can fit tooons more where before it maxed out at 20 entries, no matter the size

Show thread

direct streaming is fixed, and caching is upgraded so I'm hoping this improves cache ratio. When it's just smaller files it can fit a lot more now

Show thread

sheesh, 12 commits and a lot of improvements for synapse-media-proxy

ohhhh and I just realized another SSRF attack avenue to patch

Show thread

just happened to have restored direct streaming from remote > client which I broke...

Show thread

ever set out to rewrite something and end up fixing something totally different

haha me neither

meh 

should probably go outside but there's nothing to do there, i've been to all the parks, taken all the photo's

where a normal least-recent-used cache just removes the oldest entry when you add a new one but hit the max entry limit, this has a constraint set based on total size used, and can invalidate multiple old smaller entries to make space for a new bigger one, and as such dynamically shrinks/grows the amount of entries stored

will be used for the caching in synapse-media-proxy

Show thread

in the end didn't even use the index tracking method the Computer Organization book recommended, but instead a linked list across the Map entries

Show thread

fixed, and now my randomized cache set/get/remove testing loop is just going speedy, no crashes :))

Show thread

this code is kinda cursed? but also super cool? size based lru so it can invalidate multiple elements as needed to fit the size constraint

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.