[ENH] Multi-threaded Implementation #8

Open
opened 2024-01-09 18:24:24 -05:00 by modulatingforce · 1 comment

At the moment, the bot is really geared towards normal single-threaded Rust with async operations, but doesn't necessarily use any multi-threaded optimizations . After Prototype 1.0 is completed , there may be areas where performance could be enhanced by using other Rust / Crates multi-threaded features .

This task aims to :

  • After Prototype 1.0 is completed, review the Logic & Code structure where multi-threaded operations may be used
  • Re-read / re-learn Muli-threaded / Concurrency with Rust

Very low priority . tori mentioned multi-threaded in passing, and my mind started thinking of many areas already that could be independent of one another ; but realized it's a sit down to really drill down on where code change may be suggested and the costs/advantages of code suggestions

At the moment, the bot is really geared towards normal single-threaded Rust with async operations, but doesn't necessarily use any multi-threaded optimizations . After Prototype 1.0 is completed , there may be areas where performance could be enhanced by using other Rust / Crates multi-threaded features . This task aims to : - [ ] After Prototype 1.0 is completed, review the Logic & Code structure where multi-threaded operations may be used - [ ] Re-read / re-learn Muli-threaded / Concurrency with Rust --- Very low priority . tori mentioned multi-threaded in passing, and my mind started thinking of many areas already that could be independent of one another ; but realized it's a sit down to really drill down on where code change may be suggested and the costs/advantages of code suggestions
modulatingforce added the
Kind/Feature
label 2024-01-09 18:24:24 -05:00
modulatingforce added this to the Rust Learning project 2024-01-09 18:24:24 -05:00
modulatingforce added the
Priority
Low
label 2024-01-09 18:25:33 -05:00
modulatingforce added the
Backlog
Post_Prototype_1.0
Complexity
Expert
labels 2024-03-27 18:42:02 -04:00
modulatingforce modified the project from Rust Learning to Forcebot Prototype 1.0 Push 2024-03-27 18:46:26 -04:00
modulatingforce removed this from the Forcebot Prototype 1.0 Push project 2024-03-27 18:46:32 -04:00
Author
Owner

😆 already played around a little in #56

for _ in 1..5 {

                dbg!("Chat queue Helper thread generated");
                let r_ccc = r_cc.clone();
                let chat_c = chat_ar.clone();
                tokio::spawn(async move {
😆 already played around a little in https://git.flake.sh/modulatingforce/forcebot_rs/pulls/56 ```rust for _ in 1..5 { dbg!("Chat queue Helper thread generated"); let r_ccc = r_cc.clone(); let chat_c = chat_ar.clone(); tokio::spawn(async move { ```
modulatingforce added this to the Rust Learning project 2024-04-05 11:59:10 -04:00
modulatingforce self-assigned this 2024-04-05 11:59:15 -04:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: modulatingforce/forcebot_rs#8
No description provided.