[Bizgres-general] [ENG] Re: Statement Queuing take II - Resource Scheduling (Running with cost and cursors)

[Mark Kirkwood]

Luke Lonergan wrote:
> Mark,
>
> On 8/1/06 11:39 PM, "Mark Kirkwood" <mkirkwood at greenplum.com> wrote:
>
>   
>> I guess this is a different way of managing the system load, one way being:
>>
>> - put users into queues based on the their expected workload
>>
>> Whereas what we have been describing is:
>>
>> - put statements into queues based on their estimated workload
>>
>> It is certainly interesting...(scratches had), not sure we can do both...
>>     
>
> The latter (#2) is the one that works best to manage workload and throughput
> for the system IMO.
>
> I think admins would have too much trouble trying to force people to change
> users for different query types as implied by #1, in fact I think it won't
> work at all.
>
> Whether it is cost, memory use, or some other measure of resource
> consumption, we need to assess an execution plan's resource consumption and
> place it into the appropriate queue for execution, independent of the user
> that is connected.
>   

I guess we were all thinking along the lines of "users mainly do one 
type of workload" (which is true in some cases anyway), but clearly in 
cases where user x does several different types of workload (e.g. on 
Mondays does data mining and then daily reporting the other days....) 
what you are describing will work better.

> Sounds like we need to rework the design a bit?
>
>
>   


Yeah, fortunately the machinery to track statements and locks is pretty 
independent of how the statement gets in a queue.

Cheers

Mark