HP3000-L Archives

March 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Ranft <[log in to unmask]>
Reply To:
Mark Ranft <[log in to unmask]>
Date:
Tue, 9 Mar 1999 09:49:02 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (45 lines)
Brian,

Check to see if Speedware is locking the database (or anything else for that
matter).  If a D queue (or other lower priority) process is holding a
resource that a higher priority process needs the dispatcher temporarily
raises the priority of the D queue process to match that of the waiting
process.  This is a feature is priority boosting'.

There may be an option in Speedware to prevent it from doing locking.

To find out if database locking is occuring, sign on as the creator of the
database, run DBUTIL and do a >SHOW databasename LOCKS.

Good luck,

Mark Ranft
Mark@Pro3K,com
www.Pro3K.com



Brian wrote in message ...
>Is it possible to limit resources to a given application or session?
>Currently my HP 959ks100 works fine doing it's designated processing. Add
EZ
>reporting (Speedware)to that, and the system is a dog. I have moved the EZ
>reporting sessions to the D que which has kept the normal users in the C
que
>from suffering too badly, but periodically, the system will get saturated
>enough to cause all users to get locked up temporarily. CPU usage will hit
>100%(Lund SOS). I would like to keep the HP from getting to this point.
>
>The obvious solution is to limit reporting to off hours or get another
small
>HP box that would take care of the reporting.
>
>I'm hoping I can find an easier or less expensive solution.
>
>
>
>Brian Wolfe
>
>BCTEL Interactive
>

ATOM RSS1 RSS2