enleur
09/14/2018, 5:17 AM<http://Dispatchers.IO|Dispatchers.IO>
, now it cuts unused threads instant, but consumes more cpuelizarov
09/14/2018, 5:43 AMenleur
09/14/2018, 11:17 AMwithoutclass
09/14/2018, 12:56 PM<http://Dispatchers.IO|Dispatchers.IO>
. At about 2500 requests/second I only lost somewhere around 11% of requests. The packet loss was only because I hit the thread limit (about 90 on my machine).enleur
09/14/2018, 1:15 PMVsevolod Tolstopyatov [JB]
09/14/2018, 2:09 PMkotlinx.coroutines.scheduler.keep.alive.sec
system property and see if that helpsVsevolod Tolstopyatov [JB]
09/14/2018, 2:11 PMkotlinx.coroutines.scheduler.resolution.ns
may help as well, but is less recommendedenleur
09/14/2018, 4:22 PM1) Is this problem critical for you?No, It is not an issue. It was critical when it hanged and consumed all 4 cores 🙂 but that was fixed in 0.26
2) Could it be the case when load is increased because system has more load after 11::30?Load was stable and I think you’re right, it uses more cpu because of thread utilisation