Down at 11:00 EST
I have to take LibraryThing down tonight at 11:00 EST (8:00 PST). I'm swapping in a new server, and there's just no way to do that "on the fly."
I don't want to over-promise, but I think it will help. (It's currently calculating book recommendations, at a rate of 500/minute!) More important than any short-term speed gain, it's set up in such a way that I can snap on additional servers at need. LibraryThing has a lot of different sorts of database interactions—from catalog-display requests to highly complex social calculations. Some, like widget-serving, must never wait ten seconds. Others, like a complex all-library word search, can. Ultimately, all these different requests should not be running on one machine, and one that also serves all the web pages, etc.
Anyway, it'll be down from 11:00 tonight until some time in the wee hours.
I don't want to over-promise, but I think it will help. (It's currently calculating book recommendations, at a rate of 500/minute!) More important than any short-term speed gain, it's set up in such a way that I can snap on additional servers at need. LibraryThing has a lot of different sorts of database interactions—from catalog-display requests to highly complex social calculations. Some, like widget-serving, must never wait ten seconds. Others, like a complex all-library word search, can. Ultimately, all these different requests should not be running on one machine, and one that also serves all the web pages, etc.
Anyway, it'll be down from 11:00 tonight until some time in the wee hours.
posted by Tim at 9:14 PM
11 Comments:
http://www.librarything.com/atom.xml resolves OK for me (using intraVnews in Outlook).
Bob
Chris: It's a Blogger thing. I don't think Tim has any control over how his feed is generated. Your RSS reader must be more sensitive than mine (Bloglines), as I have no problem with the feed.
Tim: How did the transition to the new server go?
Hope everything's going well with the server move!
Well, I just entered six new books and the whole system was noticeably faster. So here's hoping it won't degrade.
Thanks, Tim. The long delays between screens were getting tedious, I must admit.
I hate to say it but it's still really slow for me )-:
I think you'll find it faster, particularly for things I have control over. (An 2-4 second wait for Amazon and a longer one for most libraries is out of my hands.)
I'm not going to announce that until I get confirmation from others, and everyone makes the final transition. By that I mean that it's currently changing DNSs (DNSes?) for the web serving. If your IPS has the old DNS you are fetching web pages from a server in New York, but the web server is fetching database content from the new machine in California. **EVEN SO** it is much faster. Once you have the new DNS, you're doing everything on a California machine, which is speedy.
You can tell which machine you're on by checking the home page. Down by the photo credit, it will either say "You are on the NY machine" or the CA one.
I'm *SO* looking forward to solving this problem for now. It's eaten up way too much of my time, time that could have gone into debugging and feature design.
Quick addition for Hippietrail:
Which interactions/pages are you finding slow? Not to dispute with you, but the "slow query report" shows that between last night and this morning no query—database interaction—took more than ten seconds. Before the move, this numbered in the hundreds.
Also, let me know which server you're on (see above about finding that on the home page).
Thanks!
One little hitch, Tim. Sorry, but since no one else seems to have mentioned it yet...
Special characters seem to have dropped out of sight again. I first noticed it on a French-language title in my collection. Then I realized that all my Kanji (Japanese) titles have dissolved into gibberish, too. (See http://www.librarything.com/catalog.php?tag=kanji+book for some examples.)
Hopefully this is just a hiccup... or possibly some seasonal Groundhoggy interference?
Just wanted to say I really appreciate the work you're putting in. This site is actually changing my life -- going through my books (I've cataloged 900 or so) has gotten me excited about reading again.
I reported chamekke's bug on the Google group last night. It seems the HTTP or HTML no longer declares the encoding to be UTF-8.
Hoorah! The Kanji titles have returned. And also the so-lovely French accents... l'accent aigu, l'accent grave, et bien l'accent circonflexe. Well done!
Post a Comment
<< Home