Entity Bean Performance

Using entity beans will probably produce worse performance than leading alternative approaches to persistence, unless your app server has an efficient distributed and transactional entity bean cache, or substantial developer effort is put into multiple deployments. In the latter case, performance will be determined by the nature of the app; apps with largely read-only access to data will perform well, while those with many writes will gain little benefit from caching. Why does this matter? Because entity bean performance, without effective caching, may be very bad indeed. Efficient performance from the entity bean model rests on the following conditions:

Why do entity beans have performance problems in many cases?

Entity beans perform particularly badly, and consume excessive resources, with large resultsets, especially if the resultsets (like search results) are not modified by users. Entity beans perform best with data that's always modified at the individual record level.