ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » limitation of local cache

Post new topic  Reply to topic
 limitation of local cache « View previous topic :: View next topic » 
Author Message
siva reddy
PostPosted: Wed Aug 31, 2016 2:13 am    Post subject: limitation of local cache Reply with quote

Novice

Joined: 16 Jul 2016
Posts: 11
Hi ,

Is there are documented limitation on the size of the cache implemented using shard row in message broker v 7.

Also , the shared row cannot scale beyond a certain limit (what is precisely the limit 3000 records / 5000 records ?), after which accessing the DB directly would give a better performance.

Global cache is only supported from v8 and hence this is not an option.


Regards,
Siva
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Aug 31, 2016 2:17 am    Post subject: Re: limitation of local cache Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
siva reddy wrote:
Hi ,

Is there are documented limitation on the size of the cache implemented using shard row in message broker v 7.

Also , the shared row cannot scale beyond a certain limit (what is precisely the limit 3000 records / 5000 records ?), after which accessing the DB directly would give a better performance.

Global cache is only supported from v8 and hence this is not an option.


Regards,
Siva

You may need to scour developerworks for the right article. They tell you there exactly how to organize your shared row cache so as to overcome that 3,000 to 5,000 record usability for access time.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
harish_td
PostPosted: Thu Sep 01, 2016 6:19 pm    Post subject: Reply with quote

Master

Joined: 13 Feb 2006
Posts: 236
This also has to do with DB/Table design. If you are required to cache a a 30 column table in ESQL Cache, you will see that the number of records that you can access faster is going to be a lot lesser than 2,000.

The below article is a great way of caching 2 columns useful for REFERENCE Code Lookup

https://www.ibm.com/developerworks/websphere/library/techarticles/1405_dunn/1405_dunn.html
Back to top
View user's profile Send private message Yahoo Messenger
fjb_saper
PostPosted: Thu Sep 01, 2016 9:42 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
harish_td wrote:
This also has to do with DB/Table design. If you are required to cache a a 30 column table in ESQL Cache, you will see that the number of records that you can access faster is going to be a lot lesser than 2,000.

The below article is a great way of caching 2 columns useful for REFERENCE Code Lookup

https://www.ibm.com/developerworks/websphere/library/techarticles/1405_dunn/1405_dunn.html

You could cache a lot more than 2 colums. What matter is the access path chosen to the data. Whether with 1 or 2 variables in the access path...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » limitation of local cache
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.