Hi, On Tue, May 28, 2019 at 11:09 PM ding peng <[email protected]> wrote: > > Yes, I also believe we need builtin benchmark for dubbo, like netty or grpc > always does(micro benchmarks based on jmh). But there are so many > configuration on registry, transport, serialization etc. for dubbo. Maybe we > just can use one certain config to implement this?
You can choose the default configuration first. Please feel free to go ahead if you would like to improve it. > > BRs > Moriadry > > > On May 23, 2019, at 1:55 PM, YunKun Huang <[email protected]> wrote: > > > > It sounds good, and using disruptor may has some performance improvement. > > > > But before do this, I think we need figure out a official way or a common > > way to do benchmark first. > > > > This project maybe a good start: > > https://github.com/apache/incubator-dubbo-benchmark but looks like it > > doesn't have update for a long time > > > > On 2019/05/21 11:50:58, ding peng <[email protected]> wrote: > >> Hi, > >> > >> There are many handler threads and worker threads in Dubbo, Do we have > >> a plan to use disruptor as one of the common thread pool implement, > >> Disruptor library is known to be one of the fastest ways of implementing > >> the queues that are required for communication between producers and > >> consumers. > >> > >> With disruptor builtin, I believe there will be some performance > >> improvement on thread pool. > >> > >> Moriadry > -- Best Regards！ Huxing
