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
Currently, Cluster.Run is executed on a dedicated threads. This is not great for several reasons:
it's a inefficient use of resource, especially when the application is connected to many clusters
it involves extra context switches
when investigating thread pool starvation, a trace could show that Cluster.Run was the method that spent the most time blocking threads. After some time, you realize that it's a in dedicated thread so it can be ignored for the investigation.
What do you think about making the Aerospike client a good citizen by turning this code async and running it in the thread pool?
The text was updated successfully, but these errors were encountered:
aerospike-client-csharp/AerospikeClient/Cluster/Cluster.cs
Line 301 in ba6b5a6
Currently, Cluster.Run is executed on a dedicated threads. This is not great for several reasons:
Cluster.Run
was the method that spent the most time blocking threads. After some time, you realize that it's a in dedicated thread so it can be ignored for the investigation.What do you think about making the Aerospike client a good citizen by turning this code async and running it in the thread pool?
The text was updated successfully, but these errors were encountered: