valeriansaliou/sonic

Make all commands ASYNC (dispatch to worker thread pool)

Open

#43 创建于 2019年3月15日

在 GitHub 查看
 (7 评论) (0 反应) (0 负责人)Rust (21,176 star) (613 fork)batch import
enhancementhelp wanted

描述

Currently, commands are processed synchronously in the channel thread. This limits parallelization on setups that open very few Sonic Channel instances, but where Sonic runs on a lot of CPUs. Currently 1 channel = 1 thread; but we'd like to make the channel protocol fully asynchronous and thus Sonic will be able to dispatch commands for work to a thread pool.

We just need to figure out how we can rework the protocol so that a RES for a REQ can be caught later on (eg. with a marker ID as we already do for search queries with PENDING?).

贡献者指南

技术栈
rust
领域
backend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Understanding of Rust asyncKnowledge of Sonic channel protocol
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
Examine the current channel thread implementation in Sonic's source code (likely in src/channel or similar). Understand how REQ/RES are matched. Consider using marker IDs similar to search's PENDING mechanism to associate responses with requests. Propose a design that uses Rust's async/await and a thread pool.