[106] in Project_DB
Fwd: Arachne seems awfully slow today.
daemon@ATHENA.MIT.EDU (Bill Cattey)
Wed Apr 30 17:44:09 1997
Date: Wed, 30 Apr 1997 17:44:03 -0400 (EDT)
From: Bill Cattey <wdc@MIT.EDU>
To: miki@MIT.EDU, project-db@MIT.EDU
Miki: would you respond to Ron's questions?
X-Andrew-Authenticated-As: 0;oglala;Super-User
Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po9.MIT.EDU (5.61/4.7)
id AA24478; Wed, 30 Apr 97 17:00:47 EDT
Received: from MITVMC.MIT.EDU by MIT.EDU with SMTP
id AA05254; Wed, 30 Apr 97 16:00:14 EST
Message-Id: <9704302100.AA05254@MIT.EDU>
Received: from MITVMC.MIT.EDU by mitvmc.mit.edu (IBM VM SMTP V2R3)
with BSMTP id 9062; Wed, 30 Apr 97 17:00:57 EDT
Received: from MITVMC.MIT.EDU (NJE origin REP@MITVMC) by MITVMC.MIT.EDU (LMail
V1.2b/1.8b) with BSMTP id 2383; Wed, 30 Apr 1997 17:00:57 -0400
Date: Wed, 30 Apr 97 16:47:33 EDT
From: Ron Parker <REP@mitvmc.mit.edu>
Subject: Re: Arachne seems awfully slow today.
To: Bill Cattey <wdc@MIT.EDU>, DS-ASK@mitvma.mit.edu
Cc: o&s-facmgt@MIT.EDU
In-Reply-To: Message of Wed, 30 Apr 1997 12:55:21 -0400 from <wdc@MIT.EDU>
On Wed, 30 Apr 1997 12:55:21 -0400 you said:
>At the moment, it is unclear to me who the appropriate person is to deal
>with this.
>Today I was helping someone use the project database, and was shocked to
>see how slow response was on Arachne.
>
>Is there some ongoing database maintenance that makes sure there are no
>gross inefficiencies creeping in?
>
>Are appropriate things being restarted on a regular basis?
>
>Neither Miki nor I consider ourselves competent judges of what is going
>on with the running system to know if there have crept in spinning
>oracle processes hogging the CPU, or if there are other appropriate
>restarts that need to occur.
>
>-wdc
Bill,
A few questions....
When and for how long did you experience slow response?
What function(s) were you executing when you experienced problems?
Were you accessing the database through the web-server?
If so, were you able to determine that there were no response issues
with:
network traffic?
the client platform (were all clients experiencing the same
behavior and only when accessing the project database)?
the web-server?
Thanks,
Ron (ds)
