Re: [wildfly-dev] Pooling EJB Session Beans per default

> Its a horrible theory. :) How many EJB instances of a give type are > created per request? Generally only 1. 1 instance of one object of > one > type! My $5 bet is that if you went into EJB code and started > counting > how many object allocations were made per request, you'd lose count > very > quickly. Better yet, run a single remote EJB request through a perf > tool and let it count the number of allocations for you. It will be > greater than 1. :) > > Maybe the StrictMaxPool has an effect on performance because it > creates > a global synchronization bottleneck. Throughput is less and you end > up > having less concurrent per-request objects being allocated and GC'd. > The number per request, while relevant is only part of the story. The number of concurrent requests happening in the server dictates the object allocation rate. Given enough concurrency, even a very small number of object allocations per request can create an object allocation rate that can no longer be sustained.