|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Default max size of runtime environment variable caching |
« View previous topic :: View next topic » |
Author |
Message
|
wmb_wps_soa |
Posted: Fri Aug 10, 2012 5:47 am Post subject: Default max size of runtime environment variable caching |
|
|
Acolyte
Joined: 19 Feb 2010 Posts: 65 Location: Detroit,Michigan,USA.
|
Hi,
Can anybody tell the max default max size of runtime environment variable caching in WMB 7.0.0.3? Also, is there any MQSI environment variable has to be changed inorder to increase the runtime environment variable caching?
Much appreciated for the inputs.
Thanks |
|
Back to top |
|
 |
lancelotlinc |
Posted: Fri Aug 10, 2012 5:55 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
On AIX 7.1 POWER7 architecture, the address space of 1 exabyte is the max on 64-bit JVMs.
I'm not sure why you want to mess up a perfectly good out-of-the-box configuration by changing it. Why not use it plug-and-play till you run into a problem? _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
wmb_wps_soa |
Posted: Fri Aug 10, 2012 6:11 am Post subject: |
|
|
Acolyte
Joined: 19 Feb 2010 Posts: 65 Location: Detroit,Michigan,USA.
|
Thank you lancelotlinc.
We have a requirement where we need to extract large data (in GB's) from DB2 database to do the transformation. I have played with the in-memory data (local and environment variable) with the size of MB's, but not in GB's. So, just want to confirm if WMB 7.0.0.3 handles that before we start the design/development.
Thank you |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Aug 10, 2012 6:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You should review the performance report for your platform.
You should review the methods you are using to process the data, to see if you can process it in small chunks rather than giant pieces. There's a "large messaging" sample that covers some of these topics.
You should review the limitations of the OS you are running your broker on, in terms of it's limits on the amount of memory that a single process can address. Remember that each EG on a broker is a separate OS level process. This means you should also consider devoting an EG to just this single flow that does this large messaging work. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Fri Aug 10, 2012 6:21 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
There are 1,024 bytes in a kb; 1,024 kbs in an mb; 1,024 mbs in a gb; 1,024 gbs in a tb; 1,024 tbs in a pb; and 1,024 pbs in an eb.
I don't think memory will be your problem if your payload is only a few GBs. I think your problems will be more along the lines of excellent coding practices rather than running out of memory. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|