Re: "X commits per minute": is there an absolute threshold ?

the redo logs groups of every member need to be one disk only for this purpose

oracle groups commits together so the number of commits is only limited by the
transfer volume of the log disk, commit syncs in pl/sql can also be "saved" in some cases
( modern disks can write 30mb per second so this is your limit )

also the most import things in application design is to reduce number of commits
commit only on logical transaction boundaries and do not commit because you think it is "faster", technical commits are nonsense with oracle !!!

so normaly if people want some numbers how fast oracle is there is something wrong ...

build your application right and it will be more than fast enough . point .

if you have 1000 users you have at max 1000 commits per minute, this is nothing

10000 users will have 10000 commits per minute , so have you more than 10000 users ??

batches have one commit, or your application is crap !

"Sebby" <sebastien.rigaud_at_b-rail.be> schrieb im Newsbeitrag news:5bc80fe2.0210310019.4338db36_at_posting.google.com...
> Hi,
> I'd just like to know if you can say that from a certain
> level, you have too many commits per minute (could it be
> 600/mn, or 5000, or 10000/mn ?), with no regard as to the
> values of yours parameters etc. whatsoever.
>
> And if no, what does this number depend on (size of rollbacks,
> init.ora parameters etc.) ? I mean if you want to ensure that
> from now on your DB will address 5000 commits/mn when you
> previously had only 200, what should you modify ?
>
> Thanks...
> Regards,
> Seb
Received on Thu Oct 31 2002 - 09:17:54 CST