After upgrading to the new transport, we are seeing a significant drop in performance for any service that take some time to execute. We have tried with the configuration used for the gateway which gave the best figures on the same hardware. We have also noted that using a separate dedicated executor thread pool, which is supported by Netty, gave much better performance than the disruptor based implementation. Even in theory, disruptor cannot give better performance when used with a real service that does some real work, rather than doing passthrough, for example. Can we improve the Netty transport to make going through disruptor optional?
-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>* *email: **az...@wso2.com* <az...@wso2.com> * cell: +94 77 3320919blog: **http://blog.afkham.org* <http://blog.afkham.org> *twitter: **http://twitter.com/afkham_azeez* <http://twitter.com/afkham_azeez> *linked-in: **http://lk.linkedin.com/in/afkhamazeez <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
