@mitesh ^ does this ring a bell?
@rahul080327 suggested I'd ping you. not sure if I was supposed to ;)
Fixed, it's back online! Need to find the time to find the root cause of this, basically we're running out of memory (most probably due to datomic)
seems to work again! 🎉 thanks!
maybe generating static HTML can prevent this problem? it's an archive right?
I can't say I haven't thought about it, but at the moment it's too much to port, and is deployed at a few more high volume slack servers. Rendering thread messages etc go back in time and update some old archives too. We also have some code related to querying for stats, showing graphs, etc. So I don't think the benefits outweigh the cost, atleast not at the moment! 🙈
I mean, the logs themselves do not change over time? So some things can just be static HTML?
> Rendering thread messages etc go back in time and update some old archives too. Ooh, aha..
Well, at least nice that you considered it :)
Yeah I think we go back and delete messages too (if we get a delete event). Not a 100% sure about this. But incremental / selective page generation is not a trivial problem to solve 😛
Also the emojis, they also update for all old messages
I thought it was as simple as IRC logs, but it sounds that it's not :)
we do honor delete messages, yes. Once logs are one to two weeks old we can generally assume they won't change any more. The original version that I inherited generated static HTML, but it meant that for every small improvement we had to rebuild the whole set going back to 2015. It was also a mess of cobbled together javascript/python tools that nobody wanted to contribute to, se we redid it as a Clojure app. Being backed by a database does give us great flexibility, the only thing I would do differently is not have it be datomic. It's not a good fit for this, and is way too resource hungry for a non-profit project.