Yep

[branchandroot]

The only thing I really have to say about AO3's latest contretemps is: I told you so~

When a platform is so fucked up that the only way to make it run is to take out the navigation, then it's time to think real hard about who's been driving development.

Comments

[niqaeli]

Oh jesus the fuck christ, the implications really just hit.

Even if they are caching the works listing, they can't be caching the sidebar if they're doing it like that. There's -- I think I need some damn smelling salts myself, now.

No wonder it's two-thirds of their load, god.

[branchandroot]

Yes! That's exactly it! I just... *waves hand wordlessly* Every. Single. Index load. Regenerated from scratch and hammering the database.

[niqaeli]

I am wistfully wishing they had been associating all the tags that ever get posted in association with a fandom in the database.

Because that would be an absolutely bizarre act of lunacy, sure, but that would be a case of what else is new hey guys the sky is blue and AO3 handles tags bizarrely.'

But... no.

I am all the fuck out of can. Also, even. I am straight up out of even. I CANNOT EVEN, BRANCH. I ACTUALLY CANNOT EVEN.

[tavella]

I did some testing a few weeks ago, and as of then, they were not caching works listings, or if there was any caching it was a matter of seconds. Every single time I clicked on a page in my "1000 works" list, it was doing a new db search. And every single time, it was regenerating the tags list for the filter. Every time I changed sorting. Every page. Every time I used the filter. Crushing the db again and again. It was jawdropping.