Hi, everyone.
New performance test has completed. In new performance test, we test one logic SQL which routes to two database in one transaction. And test result comes from test environment which 256cores and 300+G RAM The connection pool size, thread pool size of Sharding-JDBC all are 200. ---------------------- result for test environment --------------------- | Tx Type |Average response(ms)| TPS | | No Tx | 13 |13555| | saga | 15 |12726| | local | 16 |11761| | xa | 27 | 7197 | | saga with persistence | 41 | 4700 | | xa with persistence | 60 | 3322 | ------------------ Yi Yang (Sion) Apache ShardingSphere contributor ------------------ Original ------------------ From: "????????????"<tsubasa...@qq.com>; Date: Fri, Jan 4, 2019 04:24 PM To: "dev"<dev@servicecomb.apache.org>; Cc: "dev"<d...@shardingsphere.apache.org>; Subject: Re: Saga transaction performance test with Sharding-JDBC I am modifying the integration way of ShardingSphere and saga-actuator, and the next performance test will be performed after the modification is completed. ------------------ Original ------------------ From: "Willem Jiang"<willem.ji...@gmail.com>; Date: Fri, Jan 4, 2019 04:10 PM To: "dev"<dev@servicecomb.apache.org>; Subject: Re: Saga transaction performance test with Sharding-JDBC Any updated about this performance test? Willem Jiang Twitter: willemjiang Weibo: ????willem On Tue, Dec 25, 2018 at 4:31 PM ???????????? <tsubasa...@qq.com> wrote: > > XA use Atomikos as default. > > > The test run with > repo: > https://github.com/cherrylzhao/sharding-sphere-example/tree/dev-performance > module: sharding-jdbc-example --> spring-boot-nodep-example --> > spring-boot-nodep-mybatis-example > class: > io.shardingsphere.example.spring.boot.mybatis.nodep.SpringBootStarterTransactionExample > > > ------------------ Original ------------------ > From: "Zheng Feng"<zh.f...@gmail.com>; > Date: Tue, Dec 25, 2018 04:05 PM > To: "dev"<dev@servicecomb.apache.org>; > > Subject: Re: Saga transaction performance test with Sharding-JDBC > > > > Thanks for sharing these performance tests and is it possible to share the > source codes if you are happy to open these tests ? > In term of the XA tests, I think the default transaction manager is > Atomikos ? I'm interested with running with the Narayana [1] > > So it could be very useful to share the source codes with the community ! > Thanks, > > Zheng Feng > > [1] https://github.com/zhfeng/narayana-sharding-sphere > > ???????????? <tsubasa...@qq.com> ??2018??12??25?????? ????10:51?????? > > > Saga Tx is slower than No Tx. > > TPS of saga is 1700 and No Tx is 2000 in test environment. > > > > > > About the load and memory usage, we will record in next performance. > > > > > > > > > > ------------------ Original ------------------ > > From: "Zhang Yonglun"<zhangyong...@apache.org>; > > Date: Mon, Dec 24, 2018 08:56 PM > > To: "dev"<d...@shardingsphere.apache.org>; > > Cc: "dev"<dev@servicecomb.apache.org>; > > Subject: Re: Saga transaction performance test with Sharding-JDBC > > > > > > > > Impressive! > > I am focused on the performance issue of ShardingSphere for a long time, > > and have done a little saga work before. But I still can't understand why > > saga Tx faster than No Tx. Is there something I missed? > > > > BTW, I noticed that second nice machine, and wonder what's the load and > > memory usage on it when testing. > > > > > > ???????????? <tsubasa...@qq.com> ??2018??12??24?????? ????6:28?????? > > > > > Hi, everyone. > > > > > > > > > The feature of saga transaction in ShardingSphere has been basically > > > completed > > > by integrating servicecomb-saga-actuator. > > > Recently, we used Sharding-JDBC to test the performance of Saga > > > transactions. > > > > > > > > > There are results for two kinds of environments. > > > > > > > > > First result comes from local environment which including 2 cores and 16G > > > RAM > > > The connection pool size, thread pool size of saga-actuator and thread > > > pool size of Sharding-JDBC all are 50. > > > > > > > > > ---------------- result for local environment ---------------- > > > |Tx Type|Thread Number|Average response(ms)| TPS | > > > | No Tx | 50 | 337 | 140 | > > > | saga | 50 | 395 | 120 | > > > | local | 50 | 323 |143| > > > | xa | 50 | 301 |154| > > > | No Tx | 100 | 605 | 158 | > > > | saga | 100 | 789 | 120 | > > > > > > ---------------- result for local environment ---------------- > > > > > > > > > Second result comes from test environment which 256cores and 300+G RAM > > > The connection pool size, thread pool size of saga-actuator and thread > > > pool size of Sharding-JDBC all are 200. > > > > > > > > > ---------------- result for test environment ---------------- > > > |Tx Type|Thread Number|Average response(ms)| TPS | > > > | No Tx | 200 | 95 |2002| > > > | saga | 200 | 351 |1700| > > > > > > | local | 200 | 64 |2868| > > > | xa | 200 | 98 |2012| > > > ---------------- result for test environment ---------------- > > > > > > > > > And I do echo test with emptyTransport which do not execute SQL in saga, > > > the result is TPS 457 in local and 3200 in test environment. > > > > > > > > > if saga do persistence to log file, the TPS of saga will nose dive to 70 > > > in local and 600+ in test environment > > > > > > > > -- > > Zhang Yonglun > > Apache ShardingSphere
