Hi Craig, I think findAll() is different. It is a client level API and the getAll() here is for internal fetch from data cache.
In the example, when an application issue findAll() for a list of customers. It internally, for each customer with order(s), loads the "eager" relationship (orders) from data cache if they are already cached by calling map.get(orderId) for each order placed by the customer. It again load the items that are related to each order by calling map.get(itemId) for each item if the relationship to Order is declared as eager. This is potentially a performance bottleneck and findAll() does not avoid this. Thanks. Daniel On 5/23/07, Craig L Russell <[EMAIL PROTECTED]> wrote:
Hi Daniel, Take a look at the findAll(Collection oids) method of OpenJPAEntityManager. This should do a better job than N get(Object key) methods. Craig On May 23, 2007, at 3:55 PM, Daniel Lee wrote: > Do we miss the getAll(List keys) method for data cache? > > When fetching objects with eager "to-many" relationships, the code is > calling get(Object key) multiple time (one for each object in the > relationship). For example, it is doing 1 get() call for each > order placed > by a customer which we are fetching, that means 100 calls for a > customer > with 100 orders. The performance can be greatly improved if we have > getAll(List keys) methods which returns all orders in one call. > This is > especially important in a distributed environment. > > Is there a way (new plug-in) to avoid the multiple-trip for single > relationship, or can we implement the code to improve the > performance in > this area? > > Many thanks. > Daniel Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!