Entity Beans provide both data persistence and the possibility of caching objects and data in the middle-tier. The EJB 1.1
specification has three commit options which determine how EJBs are cached across transactions: Option C pools objects without
identity; Option B caches objects with identity; Option A caches objects and data. This paper explores the impact on performance
of these different commit options, pool and cache sizes on a realistic application using the Borland Application Server
EJB Entity Beans can have one of three commit options: A, B and C.