FWIW, I heard the same thing from TSM support. Others have experienced a
result similar to yours, when activating MPTHREADING !





Thomas Denier <Thomas.Denier AT MAIL.TJU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/29/2003 11:10 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Server upgrade hung


We have finally gotten some kind of resolution of one of the bugs I
mentioned in an earlier posting:

>We are still seeing the same performance bug that we had under 4.2.3.2.
>Server performance gradually degrades. When the server approaches
>complete immobility Omegamon shows it spending nearly all of its time
>doing getmain and freemain operations, even though 'show memu SHORT'
>reports Freeheld well below MaxQuickFree. We have to recycle the
>server two or three times per day.

A co-worker noticed that crippling performance problems had started
about the same time we enabled the "mpthreading" option for our server.
SMF records showed that our server was rarely using more than the
capacity of one processor, so we were not really benefiting much from
the option. Disabling the option eliminated the need to restart the
server two or three times per day. IBM's position is that there is no
evidence of a bug, and that we only saw an example of the aphorism
"your milage may vary".