One rule of thumb is "shop-to-buy-ratio". A term coined for web-based application, it denotes the ratio of transactions that only read data as opposed to the ones that really create/update/delete. In typical travel web sites (I have heard) the ratio is 200:1.
In such read-mostly scenarios an extended context can be more effective than a transactional context. On the other hand, if the transactions are predominantly write-intensive -- there is less utility in caching data across transactions in extended contexts. However, significance of this choice between the scopes of the persistence context is somewhat lessened by the usage of L2 caches especially if you use one that resides in the same memory space. ----- Pinaki -- View this message in context: http://openjpa.208410.n2.nabble.com/Persistence-Context-advice-tp5326284p5342345.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
