Re: real time app. on Oracle

"Pete Sharman" <peter.sharman_at_oracle.com> wrote in message news:acj1ju02ujq_at_drn.newsguy.com...
> In article <mA_G8.16208$b5.56603_at_newsfeeds.bigpond.com>, "Richard says...
> >
> >Hi
> >
> >I'm not entirely sure how/why you would apply suggest a definition of a
> >real-time application.
> >
> >However you might want to explore the features available with the
Database
> >Resource Manager. It provides the ability to group users into different
> >categories and define different levels of priority to each group. You can
> >also ensure that if a particular user were to use up too much resources,
it
> >can stop that unit of work from executing in the first place.
> >
> >It might be what you're looking for.
> >
> >Regards
> >
> >Richard
> >
>
> Hey, Mr Foote, good to see you contributing something useful! ;)
>
> (For those who are concerned I'm putting s**t on Richard, I am, but then
again
> I've known him for years and what are friends for? ;)
>
> One additional thing to be aware of here though is that Resource Manager
only
> kicks in when whatever resource you're talking about is maxed out e.g. CPU
has
> hit 100%.
>

Er, not true, I think. If your CPU was maxed out, what would be the point of having DBA group set to 100% at level 1, OLTP group set to 100% at level 2, and the DSS group set to 100% at level 3 (which is what the SYSTEM_PLAN does, if I recall correctly). The idea is that if I, the DBA, don't use all of my 100% allocation, the OLTP lot get 100% of whatever I have left behind. For that 'spill over' to happen, it is obvious that I must NOT be using 100% of the CPU in the first place.

Therefore, Resource Manager kicks in at all times.

Regards
HJR Received on Thu May 23 2002 - 21:27:23 CDT