We’re announcing a 90-minute downtime window this weekend starting at 11:30pm here in Boca Raton, Florida. This translates to the following times in our 5 most common timezones:

Eastern: Saturday, February 1st, at 11:30PM – Sunday, February 2nd, at 1:00AM
Central: Saturday, February 1st, from 10:30PM – Midnight
Pacific: Saturday, February 1, from 8:30PM – 10:00PM
Melbourne: Sunday, February 2nd,  from 3:30PM – 5:00PM
London: Sunday, February 2, from 4:30AM – 6:00AM

If you or your clients access a Táve link during this window, a “Maintenance in Progress” page will be displayed and will list the five timezones above.

We’ll be upgrading our primary database server software and increasing the speed and size of its storage in preparation for our major upcoming release planned for release prior to attending WPPI 2014.

Specifically, we’re upgrading the server software from MySQL 5.5 to 5.6 and increasing our storage to 100GB in order to take advantage of Amazon Web Service’s Provisioned IOPS. These improvements dramatically trim the time of the migration (and thus downtime) needed for the release mentioned above, which was 4×-6× slower and unacceptably long when tested with our current configuration.

Update: This maintenance event was performed successfully and completed ahead of schedule, allowing us to resume normal operation prior to the close of our 90-minute window. While it has been over a year since our last maintenance event, we’ll need to take another short window when rolling our our next major release, as there are substantial changes to the application and the database schema to support all the great new features in it. We’ll publish an article with the details later this month.

6 replies
    • Adrian Ziemkowski
      Adrian Ziemkowski says:

      Hey Sam,

      When you say “slow” how slow are we talking, and any particular pages? Looking at the logs, all but one or two of your requests in the past few days are showing 0.25 seconds or less on the server, with most of them under 0.15 seconds. Generally the slower pages are ones that are creating or updating data.

  1. Sam Chyung
    Sam Chyung says:

    I’m talking about my contact page. I was using a form on my WordPress install but I was getting annoyed having to copy and paste information into Tave so I spent the a few hours yesterday on the CSS and HTML to make it responsive and it just hangs on the iPhone. I took a look at the source and it’s loading a ton of scripts that I think have nothing to do with the contact page but there’s no way for me to remove them from loading. If you have an iPhone, give it a try. You’ll notice all the pages are extremely quick to load and then when you click on Contact, it takes maybe 4 or 5 seconds or more to load. I don’t seem to have the same problem on the desktop, just mobile devices.

    • Adrian Ziemkowski
      Adrian Ziemkowski says:

      Interesting. I’ll have to look into that.

      We’re changing javascript frameworks in the next major release, from YUI to jQuery, for this exact reason. The YUI framework loads a truly ridiculous number of files since they’ve modularized everything, which can be frustratingly slow on mobile (though it ought to be cached after the first load).

  2. Sam Chyung
    Sam Chyung says:

    The reality is, a person is only going to use my contact page once so it’s important to load quickly. The other issue is that the load time takes the same no matter how many times you click on the link. You can click back and then forward and it still takes 4 or more seconds to load. The first time I tried to load the contact page, I thought I broke something in the HTML or CSS and stopped looking at my iPhone. I came back after I couldn’t figure out what was wrong and discovered that the page eventually loaded. Now if I’m walking away thinking the page is broken, I can’t imagine how many other visitors are going to click on Contact, see that nothing is happening and then just click the back button or just move on to another site.

Comments are closed.