My
experience is that MTS is fine until you get into the 400 - 500 concurrent user
range, and then it goes to hell in a hand basket. The CPU usage itself will not
be very high, but that is because MTS under heavy load precludes the DB from
doing any useful work, as it spends a lot of its resources trying to manage
shared server and dispatcher processes and steps over itself trying to do what
the OS was designed to do for heavy user loads, i.e. CPU time slicing in a
bastardized form. MTS seems to give better performance under weenie-doze, but
look at what you're dealing with, a wanna-be OS that could probably use any
assistance it can get from the application (oracle rdbms).
I am
of the opinion that is is far easier to purchase more memory to run the
dedicated sessions than put yourself through the masochistic daily rituals
of trying to tune and stay on top of what MTS is doing, at least in a high user
load environment.
I have
only seen one of our customers use MTS where they had > 500 concurrent users,
and the reason I know this is because I was called out to do a performance
tuning gig on their system. The minute they turned off MTS, things started to go
much smoother. Then again, they were using 10 TCP/IP dispatcher processes
to run 2,300 concurrent users. Their DBA was still in the stage of being a DBB,
and thus still believed everything he read in the Oracle manuals, or worse
still, the press releases.
Perhaps other listers have different experiences with MTS. If so, please
share your golden nuggets of wisdom. Up to now, I am still not impressed with
the product to handle high user volumes, but am always open to someone showing
me where I am not looking.
Regards:
|
- dedicated sessions BigP
- Re:dedicated sessions dgoulet
- Re: dedicated sessions Yechiel Adar
- Re: dedicated sessions Alexandre Gorbatchev
- Re: dedicated sessions Ferenc Mantfeld
- Re: dedicated sessions Suzy Vordos