| Author |
Message
|
| nce |
 Posted: Wed Nov 22, 2006 9:54 am Post subject: MQ performance problem after migration NT -> Windows 2003 |
 |
|
Newbie
Joined: 12 Jan 2006
Posts: 6
Location: Belgium
|
Hi all,
I have a big problem.
We migrate an NT server to a server W2K3 and we reinstall all our applications on it (C, JMS).
When we launched the first tests we are very disappointed because we have very bad responses from the new W2K3 server.
Indeed, the same application, on NT takes 25ms to perform a request from a SUN Solaris server to the old server NT and answer back.
The same request from the same Solaris to the new server 2003 take 100ms !!!
We installed the same version of MQ and is 5.3 CSD9 on both wintel servers. Same version on the solaris server.
On hardware pack on the new server, there is no comparison with NT one (Hard Disk, memory, processor, ...)
Is there some tuning parameters in MQ to position specifically for W2K3 servers, or something like that on server itself ?
Have you got an idea ?
Thanks in advance. |
|
| Back to top |
|
 |
| tleichen |
| Posted: Wed Nov 22, 2006 1:13 pm Post subject: Re: MQ performance problem after migration NT -> Windows |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
| nce wrote: |
...Is there some tuning parameters in MQ to position specifically for W2K3 servers, or something like that on server itself ?
|
More than likely.... but also check what all tasks you have going on versus what was running on NT (probably much harder to quantify, from a performance point of view).
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 22, 2006 1:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And remember this might be due to an entirely non MQ cause like network having address/route resolution problems... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nce |
| Posted: Wed Nov 22, 2006 4:16 pm Post subject: |
|
|
Newbie
Joined: 12 Jan 2006
Posts: 6
Location: Belgium
|
| fjb_saper wrote: |
| And remember this might be due to an entirely non MQ cause like network having address/route resolution problems... |
No, sniffers have been installed and no network problem were detected.
They were installed one on solaris side just at put level, and on W2K3 side on get level, so at the lowest possible route.
It appears that contention might be located at this place, but I don't know what can be the behaviour difference between both plateforms (NT+2003).
If I installed CSD12, which is recommended by IBM (but not in our standard unfortunately), might it solve the problem ?
Is someone experiment it ?
Thanks. |
|
| Back to top |
|
|
| nce |
| Posted: Wed Nov 22, 2006 4:19 pm Post subject: Re: MQ performance problem after migration NT -> Windows |
|
|
Newbie
Joined: 12 Jan 2006
Posts: 6
Location: Belgium
|
| tleichen wrote: |
| nce wrote: |
...Is there some tuning parameters in MQ to position specifically for W2K3 servers, or something like that on server itself ?
|
More than likely.... but also check what all tasks you have going on versus what was running on NT (probably much harder to quantify, from a performance point of view). |
There was much more tasks and processes running on NT server than 2003.
2003 server is almost not used. It is why it's make me crazy because I don't understand this !
Normally, I should see the opposite ...  |
|
| Back to top |
|
|
| tleichen |
| Posted: Wed Nov 22, 2006 5:43 pm Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
Well, natively I would suspect that a 2003 server would have more overhead than a standalone NT system, but not to the degree of impact that you're citing here. 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 23, 2006 5:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
CSD12 is certainly going to have performance enhancements over CSD9.
If you're running Java applications, you should absolutely NOT be running CSD9.
I think what you should maybe do is turn on MQ tracing during a single request processing, and see where the most time is being spent - inside your application or inside MQ or accessing disk or network or whatever.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| nce |
| Posted: Tue Nov 28, 2006 10:13 pm Post subject: |
|
|
Newbie
Joined: 12 Jan 2006
Posts: 6
Location: Belgium
|
I installed CSD12 and nothing better.
I still have performance problem.
Now, have you got an idee on some parameters I can tune ?
Is there a manner to have the time spent between 2 queue managers ?
THanks for answers (I become crazy with this ! ) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 29, 2006 2:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| jefflowrey wrote: |
| I think what you should maybe do is turn on MQ tracing during a single request processing, and see where the most time is being spent - inside your application or inside MQ or accessing disk or network or whatever. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
