Author |
Message
|
PeterPotkay |
Posted: Sat Aug 20, 2011 1:14 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
|
Back to top |
|
 |
PeterPotkay |
Posted: Sat Aug 20, 2011 1:15 pm Post subject: Re: MQ 7 Performance Issue |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
neutron wrote: |
Me/my organization has decided to move on to linear logging due to the fact that only linear logging has the ability to do rollback of logs during a DR.
|
Please explain this. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
neutron |
Posted: Sun Aug 21, 2011 7:57 pm Post subject: Re: MQ 7 Performance Issue |
|
|
Novice
Joined: 25 Aug 2008 Posts: 21
|
PeterPotkay wrote: |
neutron wrote: |
Me/my organization has decided to move on to linear logging due to the fact that only linear logging has the ability to do rollback of logs during a DR.
|
Please explain this. |
The above statement was understood from the reply from my PMR
In response to your questions:
* Where is this transactional logs?
>>> These logs are located in /var/mqm/logs/<qmgr-name>/active
* RESET QMGR TYPE(ADVANCELOG)
1 : RESET QMGR TYPE(ADVANCELOG)
AMQ8456: Conflicting parameters in command.
>>> I suspect your qmgr does not use Linear Logging. As stated earlier Linear Logging is a prerequisite for the Backup Qmgr recovery strategy. To find out what type of logging your qmgr uses:
cat /var/mqm/qmgrs/<Qmgr-Name>/qm.ini
Under the Log: stanza, you should see either "LogType=Circular" or "LogType=Linear"
You can only use a backup queue manager when using linear logging.
Existing qmgrs that do not use linear logging will need to be recreated to use linear logging before this strategy can be employed. But
remember: existing WMQ object definitions (queues, channels, authorities
etc) can be saved and restored (SupportPac MS01) . Even queue contents can be saved and restored if necessary but not SYSTEM.* queues.
(SupportPac MO03)
* When I try to run the dis qmstatus currlog
AMQ8705: Display Queue Manager Status Details.
QMNAME(CITOS.QUEUE.MANAGER) STATUS(RUNNING)
CURRLOG( )
>>> Same reason -> circular logging
* How often do I need to replay the logs to the Backup QMGR?
>> The more often these are played, the closer the backup qmgr will be to the primary. Log files are not small so may take time to transfer.
This may be your limiting factor.
* This transactional logs contain all info like messages/queue
creation/queue deletion/channel creation/ etc???
>> From the WMQ V6 IC:
<quote>
WebSphere® MQ records all significant changes to the data controlled by the queue manager in a recovery log.
This includes creating and deleting objects, persistent message updates, transaction states, changes to object attributes, and channel activities. The log contains the information you need to recover all updates to message queues by:
* Keeping records of queue manager changes
* Keeping records of queue updates for use by the restart process
* Enabling you to restore data after a hardware or software failure
</quote>
ref:
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.amqzag.doc/fa14480_.htm |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Aug 21, 2011 8:05 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Guess you got mixed up with your support packs
Shouldn't it have said MS03 instead of MS01?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
neutron |
Posted: Mon Aug 22, 2011 12:59 am Post subject: |
|
|
Novice
Joined: 25 Aug 2008 Posts: 21
|
fjb_saper wrote: |
Guess you got mixed up with your support packs
Shouldn't it have said MS03 instead of MS01?  |
Thanks for pointing out. That was a typo mistake. |
|
Back to top |
|
 |
neutron |
Posted: Mon Aug 22, 2011 1:02 am Post subject: Re: MQ 7 Performance Issue |
|
|
Novice
Joined: 25 Aug 2008 Posts: 21
|
fjb_saper wrote: |
neutron wrote: |
Yes I am using zones for MQ7 Server. But MQ6 server is on the global zone. |
Are you aware of the file system and file speed problems being reported with Solaris zones? Do you have all your V7 files (qmgr, logs, archives) located locally or offloaded to SAN? I suggest you offload them to SAN and report back...  |
I have changed the logging to Circular.
Moved the QMgr to the global zone.
Test the run again.
Unfortunately the improvement is only 2 to 3 %.
The performance has not changed much.
I will try to see if i can setup with SANs.
Any more clues and advices that you can provide? |
|
Back to top |
|
 |
neutron |
Posted: Mon Aug 22, 2011 10:52 pm Post subject: Re: MQ 7 Performance Issue |
|
|
Novice
Joined: 25 Aug 2008 Posts: 21
|
neutron wrote: |
fjb_saper wrote: |
Are you aware of the file system and file speed problems being reported with Solaris zones? Do you have all your V7 files (qmgr, logs, archives) located locally or offloaded to SAN? I suggest you offload them to SAN and report back...  |
I have changed the logging to Circular.
Moved the QMgr to the global zone.
Test the run again.
Unfortunately the improvement is only 2 to 3 %.
The performance has not changed much.
I will try to see if i can setup with SANs.
Any more clues and advices that you can provide? |
I am seeing a 100% improvement when i move the MQ data/log files to a NFS mounted SAN directory.
The differences now between MQ6 which was 3 times faster previously and now 2 times faster is as follows:
1) MQ6 is on a direct mounted SAN directory
2) MQ6 is running on a T6xxx Oracle Sun Box, where MQ7 is running on a V8xx Oracle Sun Box (Both having same ram sizes) Can multi-threading be the cause of the 2x times slowness in this case? |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Aug 23, 2011 4:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You really should be reviewing the performance report supportPac, and understanding what it says about MQ v7 on Solaris...
You should be taking an iterative, measured, managed approach to performance tuning here. This should be backed up with metrics and statistics that show where bottlenecks are actually occurring. You aren't indicating how you are measuring your performance or what those measurements tell you.
Measurements lead to analysis, which leads to test plans, which lead to results... and results are just measurements. |
|
Back to top |
|
 |
|