eldabe: Image of canal in Venice (Default)
Eldabe ([personal profile] eldabe) wrote2012-06-10 12:49 pm

The medium would be the message. If it would load.

I know it's not AO3's fault that I haven't been able to load a page in three weeks without constantly refreshing, but it's certainly not endearing them to me. This may sound harsh, but if your site cannot handle the load, SLOW DOWN YOUR GROWTH. Limit how many fics a person can upload a day. Slow up on the invite codes. (Limit each person to two Avengers fics an hour/snark) They've said it's not a money issue, so they need to find other ways to limit traffic. *sigh*

So I'm back to browsing fic on LJ-only because if I get more than two 502 errors in a row, I give up. I just have no idea where the reams of sappy Coulon fix-its are outside of AO3. Lucky I've got a few hundred Torchwood fics saved in my rec list. *opens*

It's one of the reasons I keep cross-posting to LJ/DW and AO3, even though the Archive is much neater and prettier. I like it in so many ways, but ARGH. *headdesk*

(It is a good motivator for me to finally finish my master post! Should get on that.)
senmut: modern style black canary on right in front of modern style deathstroke (Default)

[personal profile] senmut 2012-06-10 06:33 pm (UTC)(link)
It's less the growth this time around as implementing a couple new features that aggravated the load. And now they are having to backtrack code that was evidently poorly tested, rebalance the load, and find where the memory leaks are (because really, this is a mem-leak issue or I'm a monkey's uncle, based on how bad and long it is lasting).

On the plus side, it means I can feel better about NOT writing at all this month, since my platform is crash worthy.

(The sad side of this? FF.net pissed off a lot of its user base at the same time as AO3 started the performance issues, which means AO3 is not benefitting from FF.net's tomfoolery)