Re: Connection Throttle
From: JXStern (JXSternChangeX2R_at_gte.net)
Date: 10/15/04
- Next message: JXStern: "Re: Optimizer not using the good index"
- Previous message: Quentin Ran: "Re: Subquery returned more than 1 value. This is not permitted when th"
- In reply to: Troy Murphy: "Connection Throttle"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 15 Oct 2004 09:32:34 -0700
On Thu, 14 Oct 2004 07:12:17 -0700, "Troy Murphy"
<thm92630@hotmail.com> wrote:
>I have an application that where some of the queries hit the server hard (I
>cannot rewrite the app). Some of the queries take 5 or more minutes to run
>and during this time the CPU is pegged and SQL no longer services other
>queries until the the hog query is complete. I there a way I can throttle a
>connection - like not allow a connection to use more than 25% of the CPU?
No.
Better would be a way to assign a lower priority to the offending
connection/query.
But the thinking is that this kind of thing is very dangerous, as the
throttled thread may be holding resources that block other users.
Unfortunately, you can get conditions where the range of the heavy
query is logically limited, it just soaks up all the database
capability.
If your server is otherwise large enough memory-wise and your disk
usage is appropriate (log files on separate disk from data files) and
you have two or more processors, then short of recoding, which you say
you can't do, that's it.
J.
- Next message: JXStern: "Re: Optimizer not using the good index"
- Previous message: Quentin Ran: "Re: Subquery returned more than 1 value. This is not permitted when th"
- In reply to: Troy Murphy: "Connection Throttle"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
