Looks like the app wasn’t developed with a scalable architecture from the start, then they strapped some caching out of desperation when users started flocking, and didn’t consider the invalidation parameters for private pages correctly.
It’s a little bit baffling. It’s not like they couldn’t have predicted this server load. I know it’s tricky to foresee bottlenecks in some situations but them adding caching (a very basic thing for scalability) at the last minute belies a lack of either experience, forethought, or knowledge, I am not sure which.
deleted by creator
Looks like the app wasn’t developed with a scalable architecture from the start, then they strapped some caching out of desperation when users started flocking, and didn’t consider the invalidation parameters for private pages correctly.
deleted by creator
It’s a little bit baffling. It’s not like they couldn’t have predicted this server load. I know it’s tricky to foresee bottlenecks in some situations but them adding caching (a very basic thing for scalability) at the last minute belies a lack of either experience, forethought, or knowledge, I am not sure which.
I wonder if anyone has been me
I have been you, SwallowsDick
Holy shit! It there a never tell me the odds community here? This fits like a glove
Here’s Johnny!
Did you report this (on GitHub possibly)? That seems to be a fairly important bug for the devs to get their head around.
I’ve seen the same thing when using the web interface. It’s very brief – like a flicker or something.