what do you think about subject?
I briefly experimented with BlockingWaitStrategy (we use this right now),
SleepingWaitStrategy, YieldingWaitStrategy

it seems,
 BlockingWaitStrategy - takes high CPU in one thread always ( in the thread
pool)
 YieldingWaitStrategy - CPU seems to be distributed across the pool. BUT
when the server is idle Disruptor eats lot of CPU doing thread.yield().
therefore not good.

SleepingWaitStrategy - CPU consumption is less. we need to check latency
introduced by thread.sleep ( over blocking wait)


regards,
-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 772534930
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to