Re: [infinispan-dev] The reason(s) why we have so many threads are spawned in the testsuite
On 10/09/2009 05:49 PM, Vladimir Blagojevic wrote:
On 09-10-09 11:32 AM, Galder Zamarreno wrote:
>
> On 10/09/2009 04:19 AM, Vladimir Blagojevic wrote:
>
>> Galder,
>>
>> Under profiler none of these seem to be a big problem except
>> asyncTransport TPE. All of these threads that you saw in thread dumps
>> are related to rehash requests spawned by LeaveTask. LeaveTask tries to
>> submit request to TPE and is block waiting. All of these threads are. I
>> am still trying to figure out what is going.
>>
> Block waiting where?
>
ExecutorService#submit(Callable)<---- profiler shows thread is blocked here
RPCManagerImpl#invokeRemotelyInFuture
Hmmm, that block could be due to asyncTransport thread pool being too
small although I can't see the exact line where this condition would
stop. I didn't see such thing in previous thread dumps I've taken.
I don't have time to look at it right now but a quick way to figure out
whether this is causing the slowdown would be to modify
GlobalConfiguration to look like this:
public static GlobalConfiguration getClusteredDefault() {
GlobalConfiguration gc = new GlobalConfiguration();
gc.setTransportClass(JGroupsTransport.class.getName());
gc.setTransportProperties((Properties) null);
Properties p = new Properties();
p.setProperty("threadNamePrefix", "asyncTransportThread");
->> p.setProperty("maxThreads", 10);
gc.setAsyncTransportExecutorProperties(p);
return gc;
}
That will increase the asyncTransport pool from 1 to 10 threads.
Sorry for some reason there is no copy-paste feature for a thread stack
in the profiler! I took a snapshot 3/4 into test suite and there more
than 20 threads blocked in the same line code.
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache