I think probably the easiest thing to do is just mv reporter.php and
submit.php so that mtt clients and individuals browsing will not be
able to access it.
On Aug 26, 2007, at 10:58 PM, Josh Hursey wrote:
> Jeff and Ethan,
> How do I shutdown the MTT server? Do I just log into milliways as
> mtt, or can I disable it from my user?
> -- Josh
> Begin forwarded message:
>> From: Josh Hursey <jjhursey_at_[hidden]>
>> Date: August 24, 2007 1:37:18 PM EDT
>> To: General user list for the MPI Testing Tool <mtt-users_at_open-
>> Subject: [MTT users] MTT Database and Reporter Upgrade **Action
>> Reply-To: General user list for the MPI Testing Tool <mtt-
>> Short Version:
>> The MTT development group is rolling out newly optimized web frontend
>> and backend database. As a result we will be taking down the MTT site
>> at IU Monday, August 27 from 8 am to Noon US eastern time.
>> During this time you will not be able to submit data to the MTT
>> database. Therefore you need to disable any runs that will report
>> during this time or your client will fail with unable to connect to
>> server messages.
>> This change does not affect the client configurations, so MTT users
>> do *not* need to update their clients at this time.
>> Longer Version:
>> The MTT development team has been working diligently on server side
>> optimizations over the past few months. This work involved major
>> changes to the database schema, web reporter, and web submit
>> components of the server.
>> We want to roll out the new server side optimizations on Monday, Aug.
>> 27. Given the extensive nature of the improvements the MTT server
>> will need to be taken down for a few hours for this upgrade to take
>> place. We are planning on taking down the MTT server at 8 am and
>> we hope to have it back by Noon US Eastern time.
>> MTT users that would normally submit results during this time range
>> will need to disable their runs, or they will see server error
>> messages during this outage.
>> This upgrade does not require any client changes, so outside of the
>> down time contributors need not change or upgrade their MTT
>> Below are a few rough performance numbers illustrating the difference
>> between the old and new server versions as seen by the reporter.
>> Summary report: 24 hours, all orgs
>> 87 sec - old version
>> 6 sec - new version
>> Summary report: 24 hours, org = 'iu'
>> 37 sec - old
>> 4 sec - new
>> Summary report: Past 3 days, all orgs
>> 138 sec - old
>> 9 sec - new
>> Summary report: Past 3 days, org = 'iu'
>> 49 sec - old
>> 11 sec - new
>> Summary report: Past 2 weeks, all orgs
>> 863 sec - old
>> 34 sec - new
>> Summary report: Past 2 weeks, org = 'iu'
>> 878 sec - old
>> 12 sec - new
>> Summary report: Past 1 month, all org
>> 1395 sec - old
>> 158 sec - new
>> Summary report: Past 1 month, org = 'iu'
>> 1069 sec - old
>> 39 sec - new
>> Summary report: (2007-06-18 - 2007-06-19), all org
>> 484 sec - old
>> 5 sec - new
>> Summary report: (2007-06-18 - 2007-06-19), org = 'iu'
>> 479 sec - old
>> 2 sec - new
>> mtt-users mailing list
> mtt-devel mailing list