You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Frequent use of std::sync::Mutex in ipstack causes performance issues #62
In the ipstack, we frequently use std::sync::Mutex, which can lead to performance degradation due to thread blocking. Ideally, we should replace these with non-blocking synchronization mechanisms to prevent thread contention and improve performance.
changed the title [-]Frequent use of std::sync::Mutex in ipstack causes performance issues[/-][+]Frequent use of `std::sync::Mutex` in ipstack causes performance issues[/+]on May 7, 2025
Activity
[-]Frequent use of std::sync::Mutex in ipstack causes performance issues[/-][+]Frequent use of `std::sync::Mutex` in ipstack causes performance issues[/+]ssrlive commentedon May 8, 2025
There is currently no known approach to use a
tokio::sync:Mutexin bothtcp_main_logic_loopandpoll_readat the same time.But I don't think the performance bottleneck is here.
SajjadPourali commentedon May 8, 2025
There are some tricks including the following approach, however its implementation in our code is not straightforward.
I’m not sure about its impact on performance; we can also run a profiler like pprof-rs to evaluate it.