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.