atg locked caching - how locked caching works with atg repositories

Suggested use : when data changed frequently.
Disadvantage  : can lead to deadlocks.

<item-descriptor name="..." cache-mode="locked">

Locked caching is based on write locks and read locks.If no servers have a write lock for an item,any number of servers may have a read lock on that item.When a server requests a write lock,all other servers are instructed to release their read locks.Once an item is write locked,no other servers may get a read lock or write lock until the first server releases its write lock.In other words,once a server has a write lock on an item,all access to that item is blocked until the write is completed.

A server requests a read lock the first time it tries to access an item.Once the server has a read lock on the item,it holds that read lock until the lock manager notifies the server to release its read lock.At that time ,it drops the item from its cache.

A write lock is requested whenever a server calls getItemForUpdate(),or the first time setPropertyValue() is called,and released at the end of the transaction.

ATG Full Deployment Vs Incremental Deployment

Full Deployment

Full deployment can be useful in the case when the assets on the target sites are modified manually or are corrupted.

Target site might become inconsistent if a failure occurs during rollback,doing a full deployment,the previous set of assets created by different projects will become the  active assets of target site.

Always gives the fresh latest version data to the target

It can be time consuming as the all target data first purged then deployed again with previously deployed projects. It consumes number of resources on the target.

Incremental Deployment

It’s useful in the case when the assets which are deployed to the target are less in number after the first deployment.

Whenever you have a need to rollback to the previous completed project then the incremental deployment is preferred to do because the full deployment will try to delete the all data from the target which can not be restored again.


1. Faster than full deployment since only the assets in the project are being purged first and then deployed.
In case of multiple deployments in a day, Incremental deployment is preferred.

No drawback. Once the data is imported to the target, the deployment happens incrementally.

NIIT National Chess Championship Rules and Regulations

 1. Any 4 players can play in each round of Team Championship.However, all   
   6 players are eligible to take part in the Individual Round. 
2. Team can be formed with both Male & Female members. 
3. Those players who are within the first 20 ranking of the 
   Individual Championship will be eligible to play against 
   Anand. They will be allowed to bring in 2 more players from
   his/her organisation to assist him/her. These 2 additional 

   players    should be from HR & Top Management, preferably. 
   These 2 additional players cannot be from the original playing 
   squad. 
4. All Playing Conditions, Rules & Regulations will be decided by  
   State Chess Association(In Bangalore -> United Karnataka Chess 
   Association (R)) as per the International Playing terms& conditions. 
5. The Winning Team of Team Championship will get a direct entry 
   into 2012/13 National Team Championship. 
6. The Winner of Individual Championship will get a direct entry 
   in to 2012/13 National B Championship for Individuals. 
7. The Championship shall be played under the laws of "Chess and
   FIDE Swiss Rules”. Totally Seven rounds shall be played    

   unless otherwise decided by the Championship committee before 
   the commencement of the Championship.
8. Team Championship: Each Team consists of 6 players out of 
   which any 4 appointed by the team captain will play each 
   round.
9. Individual Championship
   Div. I: For Rated players. Unrated players can also opt to 
   play if they desire.
   Div. II: For Unrated players only.
10. The time control will be 
   A. 45 minutes for each player for Team Rounds
   B. 30 minutes for Individual Rounds. 
   However, the Championship committee has the right to change 
   the above timings or the number of rounds before the    
   commencement of the first round.

Participation fee:

a. Rs 12,000 for each corporate team (6 players for both  
   individual and team events)
b. Rs 4,000 for individual entries. 

Prizes:

Total Cash & Trophies worth nearly Rs. 2.00 lakhs will be awarded to the three highest placed teams in the Team Championship, three highest placed individuals in the Individual Championship Div I & II respectively, Top Board Prize, 2nd.Board, 3rd. Board, 4th. Board for Team Championship & Most Promising Women Player of the Championship.

hitRatio missRatio and usedratio in repository caching


The missRatio indicates that the items in cache are not used or missed. That is your queries are returning totally different rows of data everytime and hence having a chance for them is useless. Look for a high missRatio and disable cache for these items.


Same way if the missRatio is too low or the hitRatio is too high something like 90-95%, that means that we have almost all the data in the cache itself. This indicates that either our cache size is too big or the data in the table is not in large numbers.


The usedRatio indicates the percent of the maximum cache size now in use. If this is too high, that means that most items in the cache are being used now. So we can increase the cache size.


The usedRatio is the percent of  entryCount/cache size.  gives the number of entries currently in the cache. If this is same as your cache size consider increasing the cache size.
Related Posts Plugin for WordPress, Blogger...