WIP: issue-routine-lock-idea2 #56
1 changed files with 1 additions and 1 deletions
|
@ -145,7 +145,7 @@ impl Chat {
|
|||
|
||||
modulatingforce marked this conversation as resolved
|
||||
// loop {
|
||||
// Spawn x helper threads to process messages in the outqueue
|
||||
for _ in 1..10 {
|
||||
for _ in 1..5 {
|
||||
|
||||
dbg!("Chat queue Helper thread generated");
|
||||
let r_ccc = r_cc.clone();
|
||||
|
|
Loading…
Reference in a new issue
The following and patterns like this involving a
loop
and innertokio::spawn
are likely why we're seeing large memory usage with this changeloop {
let r_ccc = r_cc.clone();
let chat_c = chat_ar.clone();
tokio::spawn(async move {
Recommendation
for
loop instead of a infiniteloop
The above helped the spawning and high memory usage