Re: [OMPI devel] MTT database

2017-10-17 Thread Josh Hursey
I just re-activated the MTT server.

I took the downtime opportunity to push some of the local changes that had
accumulated back to the MTT repo - this did require some code changes. It
looks like everything is operating normally now, but let me know if you
have any problems with the server.

-- Josh


On Thu, Oct 12, 2017 at 12:30 PM, Josh Hursey  wrote:

> It looks like the AWS database is unreachable. From the dashboard it looks
> like we exhausted disk space, which might be the root cause. From the logs
> I can see on the Dashboard, it looks like the psql daemon failed to
> restart...
>
> I can free up database space, if I can attach to the server. I'm not sure
> how to do that though without Brian's help.
>
>
> On Thu, Oct 12, 2017 at 10:20 AM, Howard Pritchard 
> wrote:
>
>> is anyone seeing issues with MTT today?
>> When I go to the website and click on summary I get this back in my
>> browser window:
>>
>> MTTDatabase abort: Could not connect to the ompidb database; submit this
>> run later.
>>
>> Howard
>>
>> ___
>> devel mailing list
>> devel@lists.open-mpi.org
>> https://lists.open-mpi.org/mailman/listinfo/devel
>>
>
>
>
> --
> Josh Hursey
> IBM Spectrum MPI Developer
>



-- 
Josh Hursey
IBM Spectrum MPI Developer
___
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel

Re: [OMPI devel] MTT database

2017-10-12 Thread Josh Hursey
It looks like the AWS database is unreachable. From the dashboard it looks
like we exhausted disk space, which might be the root cause. From the logs
I can see on the Dashboard, it looks like the psql daemon failed to
restart...

I can free up database space, if I can attach to the server. I'm not sure
how to do that though without Brian's help.


On Thu, Oct 12, 2017 at 10:20 AM, Howard Pritchard 
wrote:

> is anyone seeing issues with MTT today?
> When I go to the website and click on summary I get this back in my
> browser window:
>
> MTTDatabase abort: Could not connect to the ompidb database; submit this
> run later.
>
> Howard
>
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/devel
>



-- 
Josh Hursey
IBM Spectrum MPI Developer
___
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel

Re: [OMPI devel] MTT Database and Reporter Upgrade **Action Required**

2007-08-27 Thread Josh Hursey
Just wanted to let everyone know that the server upgrade went well.  
It is currently up and running. Feel free to submit your MTT tests as  
usual.


Cheers,
Josh

On Aug 24, 2007, at 1:45 PM, Jeff Squyres wrote:


FYI.  The MTT database will be down for a few hours on Monday
morning.  It'll be replaced with a much mo'better version -- [much]
faster than it was before.  Details below.


Begin forwarded message:


From: Josh Hursey 
Date: August 24, 2007 1:37:18 PM EDT
To: General user list for the MPI Testing Tool 
Subject: [MTT users] MTT Database and Reporter Upgrade **Action
Required**
Reply-To: General user list for the MPI Testing Tool 

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
installations.

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-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users



--
Jeff Squyres
Cisco Systems

___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel