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
I dig a lot of resources and still can not find out a propper and most performant way on how to send a lot of different HTTPS requests using simple Console .Net Core app.
Lets imagine that there are 1000 different servers (and different urls) which you need to crawl/request constantly every second. Each server supports different HTTP Protocol versions and different TLS versions.
Using HttpClient per Url and SendAsync method seems like not the best way. We get a lot of timeouts, TLS/Decryption errors, connection errors and other errors/exceptions.
Also it is not obvious on how to make +1000 requests per second. Using Task.Run per request seems just pooling a lot of method calls / requests which later just timed out.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I dig a lot of resources and still can not find out a propper and most performant way on how to send a lot of different HTTPS requests using simple Console .Net Core app.
Lets imagine that there are 1000 different servers (and different urls) which you need to crawl/request constantly every second. Each server supports different HTTP Protocol versions and different TLS versions.
Using HttpClient per Url and SendAsync method seems like not the best way. We get a lot of timeouts, TLS/Decryption errors, connection errors and other errors/exceptions.
Also it is not obvious on how to make +1000 requests per second. Using Task.Run per request seems just pooling a lot of method calls / requests which later just timed out.
Thanks for any help
Beta Was this translation helpful? Give feedback.
All reactions