DB1 experiencing slowdowns

About an hour ago, DB1 (our first database server) started acting up and going REAL slow, and we ended up rebooting it. It ran a self-check on the database which delayed it another 45 minutes, but now it is done and processing traffic normally. However, it will take a while to catch back up with real time.

All site IDs below 15,000 or so are on this server. For future reference, to find out what server any of your sites are on (each one could theoretically be on a unique server), hit your site preferences page. It's one of the items listed on that page.

Reader Comments

Well, good news is that it just finished and is processing normally now, so it's less than an hour behind at this moment, and should be caught up within a few hours.

Sean (Clicky) Feb 12 2008 10:53am

Thanks for the update, but I still feel like I'm being punished for signing up early :(

Sharon Feb 12 2008 11:07am

Sorry :(

Sean (Clicky) Feb 12 2008 12:58pm

"Thanks for the update, but I still feel like I'm being punished for signing up early :("

LOL

Wes Maher Feb 12 2008 9:32pm

Clicky is Awesome! I just thought I sent the random comment, I use it tooooo much everyday lol. It's Great!

Wes Feb 15 2008 12:04pm

Sean, Don't you have a plan to move / re-distribute the records to new servers?

Btw, I am lucky. All my sites are above 15000.

Ameer Feb 15 2008 12:19pm

Uh - calm down everybody... DB1 may be a bit overloaded but anyway Clicky IS great and it'll stay great.

I am on db1 but hey - we've real time stats and a good api... and we have this without having to pay for it (I do - but just because I wanted to support the clicky-Team and like the premium features ;-)

When they start to get new servers in exchange for the old ones we'll be the first to be on one of them - I am sure.

Xel Feb 15 2008 12:50pm

Why is there no longer a blog link on the footer??

Steven Feb 24 2008 4:08pm

When I post here about software updates, often times those updates not been applied to the Freewebs Clicky yet, which causes lots of confusion. So I figured removing the blog from the Freewebs site was a good intermediate solution.