Alex Chi Z.
Alex Chi Z.
I've created a GitHub project for this repo https://github.com/tikv/agatedb/projects/1
Seems that this is how thread pool is expected to work. It's more appropriate to use std::thread in agatedb, as we need long running threads instead of spawning short-running tasks.
From yatp source code, it by default spawns a maximum of `num_cpu` threads. https://github.com/tikv/yatp/blob/master/src/pool/builder.rs#L37 Therefore, (from my understanding, if threads in thread pool won't be preempted), there would have at...
> How about setting a larger capacity? If we have 5 threads, and the thread pool always has these 5 threads running, there seems no difference with `std::thread` :( Anyway,...
Related issue: https://github.com/tikv/tikv/issues/6402
To integrate with TiKV, we will only need to implement managedTxn mode. `ManagedTxns` in unistore-badger differs from original badger implementation. We will first implement badger managedTxn mode, and then migrate...
Thanks for your advice! By the way, our data fetcher is at https://github.com/SJTU-Plus/course-plus-data/tree/master/course_plus_data_fetcher . If possible, you could also help us implement this functionality.
Yes, I just found these data has already been fetched. We could later show them on frontend and update them after each round. This is some kind of future work,...
研究生系统的数据抓取比较麻烦，目前没有添加的计划。
> 全國數萬名網友的牛子（指正） 😂