So that attracted lots of bots spamming the wiki page. Thanks to Ryan Wick for noticing that, restoring the page, and protecting it so you need a login to edit, and noticing that the high google rank was what was drawing the spambots.
But that page had on it a link to my umlaut link resolver.
Nah, that’s probably too crazy. My umlaut server is probably just plain under-powered and under load (got to seperate MySQL to it’s own server). And my catalog software is probably (probably?) just crappy unstable proprietary software.
But there’s some mystery to why my catalog server has become so much less stable than it used to be. And why the umlaut server is under so much more load than it used to.
If I actually kept my logs and could compare current umlaut traffic to previous, it might be a clue, but I don’t, and I really have no idea what reasonable traffic on it is. The ajax in the background stuff does lead to lots of http requests.
Well, first step moving MySQL to a seperate server. And first step for the catalog is continuing to hate it.