[504] in Tooltime

home help back first fref pref prev next nref lref last post

Re: Scopus changes/showstoppers

daemon@ATHENA.MIT.EDU (Debi Fuchs)
Thu Nov 13 13:22:34 1997

In-Reply-To: <v03020909ff0483ce18b7@[18.81.0.146]>
Date: Thu, 13 Nov 1997 13:22:39 -0500
To: tooltime@MIT.EDU
From: Debi Fuchs <debi@MIT.EDU>

Hello,

I tested the find open scripts on some machines.  They seem to be fast on
the production database and okay on the test database.  Perhaps someone
fixed something or Steve did some indexing last night?

I'm not sure why the Test Database was reacting so much slower than
production.  Is it because the Find Open script is different, or is there
some other reason?


Results:
--------

Production Database: Real data, old scripts

   Mac           9 seconds for "Find Open"
                      (about 2.5K records, about 700 found)

   UNIX         12 seconds for "Find Open"
                      (about 2.5K records, about 700 found)

     NT          2 seconds!
                      (about 2.5K records, about 700 found)

Test Datatabase: Fake data, new scripts:

   NT machine   29 seconds for "Find Open HelpDesk" on Test database
                      (about 15K records, about 200 found)
   Mac          17 seconds for "Find Open HelpDesk" on Test database
                      (about 15K records, about 200 found)


UNIX: SPARCstation 4
NT  : Dell Dimension XPS P133c
MAC : PowerMac 7100/80


Find Pending in the Helpline Log took 33 seconds.


Cheers,
-Debi


At 10:44 AM -0500 11/13/97, Barbara Goguen wrote:
>Could someone else test the find open scripts?  They seemed to be REALLY
>slow for me yesterday, and this might be problematic if not a show-stopper.
>People currently rely pretty heavily on running a find pending script and
>if it takes a really long time to run, they are going to be impeded in
>their work.
>
>At 10:35 AM -0500 11/13/97, Debi Fuchs wrote:
>>Hi there,
>>
>>
>>>Barbara Goguen wrote:
>>>- Find Open script is still showing frozen logs, regardless of date but
>>>that might be because the freeze until date is not being written to the
>>>database.
>>
>>I changed the "find open" script last night such that it does not show
>>frozen logs.
>>
>>
>>
>>>Barbara Goguen wrote:
>>>- Thaw changed to Close on Thaw.  Couldn't test this because couldn't get
>>>#Freeze until field to store any data.  I would type in a date in Freeze
>>>until and as soon as I saved it would disappear.  When I called log back up
>>>the date would not be there.  This field appears to not be saving to the
>>>database.
>>
>>This is a showstopper and needs to be fixed before we release.
>>
>>
>>
>>>Barbara Goguen wrote:
>>>- Taken field still shows legacy users.
>>
>>The Taken field POPUP MENU should show only active users.  The Taken field
>>should allow legacy users, i.e.
>>
>>the popup menu should show:
>>  "select login_name from profiles where security_level IN
>>('ISHELP','ADMIN')"
>>the field should allow:
>>  "select login_name from profiles"
>>
>>
>>>Barbara Goguen wrote:
>>>-IP address does not yet appear as read-only on network screen.
>>
>>I think this was added... Not a showstopper but would be nice.
>>
>>
>>Cheers,
>>-Debi
>>
>>
>>-------------
>>Debi Fuchs, Consultant
>>MIT Information Systems
>>Computing Help Desk Group
>>77 Massachusetts Avenue, 11-319
>>Cambridge, MA  02139
>>(617) 253-7812
>>debi@mit.edu



-------------
Debi Fuchs, Consultant
MIT Information Systems
Computing Help Desk Group
77 Massachusetts Avenue, 11-319
Cambridge, MA  02139
(617) 253-7812
debi@mit.edu



home help back first fref pref prev next nref lref last post