You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shardingsphere.apache.org by Zhang Yonglun <zh...@apache.org> on 2019/12/09 04:47:05 UTC

Schedule for Performance Test display

Hi,

Since the performance test display is so important that has impacted the
4.0.0 release. All the work below should be finished by the end of this
week.

1. Add a scenario for Master-Slave. r/w to the same database compare with
r/w split.
2. Describe the testing scenario in detail, including node(s) SQL routed,
request concurrency, data volume.
3. Document for the performance test. Others can reproduce this test
following this document.

Any suggestions?



Zhang Yonglun
Apache ShardingSphere

Re: Schedule for Performance Test display

Posted by Zhang Yonglun <zh...@apache.org>.
I agree with you. The performance data is the most important aspect, should
be finished before others.


Zhang Yonglun
Apache ShardingSphere


zhangliang@apache.org <zh...@apache.org> 于2019年12月9日周一 下午2:31写道:

> These 3 tasks are good enough for finish all performance test issue. I
> think they should not as block issues of release.
> How about change the block issue as know the actual performance data?
>
> ------------------
>
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>
>
> Zhang Yonglun <zh...@apache.org> 于2019年12月9日周一 下午12:47写道:
>
> > Hi,
> >
> > Since the performance test display is so important that has impacted the
> > 4.0.0 release. All the work below should be finished by the end of this
> > week.
> >
> > 1. Add a scenario for Master-Slave. r/w to the same database compare with
> > r/w split.
> > 2. Describe the testing scenario in detail, including node(s) SQL routed,
> > request concurrency, data volume.
> > 3. Document for the performance test. Others can reproduce this test
> > following this document.
> >
> > Any suggestions?
> >
> >
> >
> > Zhang Yonglun
> > Apache ShardingSphere
> >
>

Re: Schedule for Performance Test display

Posted by "zhangliang@apache.org" <zh...@apache.org>.
These 3 tasks are good enough for finish all performance test issue. I
think they should not as block issues of release.
How about change the block issue as know the actual performance data?

------------------

Liang Zhang (John)
Apache ShardingSphere & Dubbo


Zhang Yonglun <zh...@apache.org> 于2019年12月9日周一 下午12:47写道:

> Hi,
>
> Since the performance test display is so important that has impacted the
> 4.0.0 release. All the work below should be finished by the end of this
> week.
>
> 1. Add a scenario for Master-Slave. r/w to the same database compare with
> r/w split.
> 2. Describe the testing scenario in detail, including node(s) SQL routed,
> request concurrency, data volume.
> 3. Document for the performance test. Others can reproduce this test
> following this document.
>
> Any suggestions?
>
>
>
> Zhang Yonglun
> Apache ShardingSphere
>