talent-plan icon indicating copy to clipboard operation
talent-plan copied to clipboard

TP201 Project3: write benchmark comparison between kvs and sled

Open xuyifangreeneyes opened this issue 5 years ago • 3 comments

General Question

I am writing TP201 Project3. When doing write benchmark, I find that sled's set operation is much slower than kvs. Screen Shot 2021-01-09 at 12 06 15 AM

I also run the Project3 code in this repo and find similar phenomenon. Screen Shot 2021-01-08 at 11 38 32 PM Write benchmark for sled takes so much time that it is not yet finished in the snapshot.

Is it normal that sled's set operation is much slower than kvs or I made mistakes somewhere.

Tips

Expect for asking questions on Github, you can also discuss it in the channel #wg-talent-plan-courses. of tidbcommunity slack workspace.

xuyifangreeneyes avatar Jan 08 '21 16:01 xuyifangreeneyes

Maybe the sled's flush is too expensive

TheLudlows avatar Jan 25 '21 03:01 TheLudlows

Same here. In my old Intel mac laptop, it takes > 1 hour for the 100 samples, while only 3-5 secs for the referenced solution and my own solution.

dreamerlzl avatar Jun 19 '22 14:06 dreamerlzl

The same issue. In my case helps to upgrade the version of criterion to 0.5.1 version. A new version of the library better adapt for slow sources

Tom910 avatar Mar 05 '24 17:03 Tom910