I'm not surprised at all that your batch jobs improved so much. MTS works
best for applications with high think time (email and so on). Batch jobs
should nearly always run in dedicated server mode because there is no time
between one statement completing and the next one starting. Just use a
different connect string to ensure you get that.
I haven't checked the section you refer to in Tom's book, but it presumably
says much the same thing (and knowing Tom, he'll correct me if I'm wrong
anyway!) ;)
--
HTH. Additions and corrections welcome.
Pete
Author of "Oracle8i: Architecture and Administration Exam Cram"
Now got a life back again that the book is released!
"Controlling developers is like herding cats."
Kevin Loney, Oracle DBA Handbook
"Oh no, it's not. It's much harder than that!"
Bruce Pihlamae, long-term Oracle DBA
"Ban Spam" <ban-spam_at_operamail.com> wrote in message
news:Xns913EB5657F3BESunnySD_at_24.0.3.73...
> "Spencer" <spencerp_at_swbell.net> wrote in news:Txrz7.451$Ol3.274357337
> @newssvr11.news.prodigy.com:
>
> > Everyone,
> >
> > Thanks in advance for any information or insight you can provide.
> >
> > The company I work for is currently assessing the viability of the
> > multithreaded server (MTS) feature of Oracle8i. (Specifically,
> > Oracle Enterprise Server 8.1.7.2.0 for Sun sparc Solaris 5.7)
>
> Tom Kyte's book warns against using MTS where there will be "long
> running transactions".
>
> I had a system where nightly batch jobs were being run into an
> instance via MTS. These jobs took 4 - 6 hours to complete. Once
> I brought the same jobs into the same system via DEDICATED
> connections the run times dropped to just under 60 minutes!
Received on Fri Oct 19 2001 - 09:30:22 CDT
