Clojurians Log v2

Did 🙂 Tried to completely unwind from work thoughts. Managed to get there just by the end of the free days 😄

How about you?

I was supposed to have Thu/Fri and Mon/Tue off, but an emergency at work Thursday evening meant I was back at work Friday and had to work through the weekend 😞 So I got 1 of my 4 days off.

Damn, that sucks @seancorfield. Can you at least take the days off some other time?

Oh yeah, once we're through this, I'll get all the time back (and more, I expect), but I think it's going to be a very busy few weeks, unfortunately.

Whoah 😞 Hope you didn't miss out on any planned social activities.

Luckily, no...

I had to cancel my original plans, so no traveling, but disconnected properly! Getting back to work again felt good yesterday.

It's good to disconnect from time to time. I'm very bad at really not being online.

I started tending to plants again within the past few days, and I thought, I wonder if Arne is growing anything now... 😌

sorry to hear that actually.

I mean, I think some kind of caching was definitely needed. But there has been, and continue to be, issues with what was chosen.

What's that, some sort of inverse survivorship bias? We live with whatever is chosen at some point, and all choices have trade-offs. Since we experience the trade-offs (particularly the negative sides) of a particular choice, we get to complain about that particular choice, without ever really knowing whether things would be better, or just shite in a different way, had we gone with a different choice.

Inverse survivorship bias? just dying? but, yes I catch your drift. complaining about what goes wrong is very easy

From Wikipedia: "Survivorship bias or survivor bias is the logical error of concentrating on entities that passed a selection process while overlooking those that did not. This can lead to incorrect conclusions because of incomplete data. " https://en.wikipedia.org/wiki/Survivorship_bias Actually, I suppose what I am describing is just vanilla survivorship bias, but with the twist that the "survivor" is viewed in a negative light rather than a positive light. But the bias (and potentially incorrect conclusions) are still due to incomplete data.

Is there a war story attached?

Ah you mention a memory leak in a later comment

yeah sorry, should have been in the thread

Nicely done. Can you save the implementation by using a limited core.cache instance or something?

This is some home brewed stuff (you know how it goes here 😛 ), and it's kind of intertwined with other stuff. Overall, there's a lot of "choosing easy over simple and suffering the consequences" going on here, I'd say. There's more stuff to untangle, but for now, the issue is that some of the keys that are used for persisting individual cache items are insanely big, and I believe can save that simply by using hashed values instead of the current values for the keys. That still leaves the issue of figuring out why the current keys are so huge and how to avoid it, since the key implementation is tied to cache invalidation and therefore is a more complex issue, but I'll take it one step at a time - key size is causing production issues all over, so getting a fix in quick would be awesome.

(And it's also tough and time consuming to debug the huge keys simply because I run out of memory and have long feedback loops due to the huge keys 😄 )

Alex always says: measure first

Wise man