Observatory and burstObservatory #4076
FightingForFun
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In the case of Observatory, it would be beneficial to have:
In case Google and all related services are not available in my country, I would like to check servers using a site like
"probeURL": "https://aliexpress.com/"
or any other, and for this, it would be useful to have"expected HTTP response code" ["200"]
// "301", "400" ..."enableConcurrency": false
- slow, one by one, but that's fine.However, if
"enableConcurrency": true
, it would be useful to have a"Number of simultaneous checks"
option, as checking 500+ servers can create a significant load on the system.In the case of burstObservatory, it would be beneficial to have:
The same:
"Number of simultaneous checks"
as checking 500+ servers can create a significant load on the system.If the checks are done in parts, 20 at a time (or whatever number we specify), it would be really great.
Checking 500 at once is too much, but doing it like this: 20 checked, next 20, checked, next 20...
Strategy: random and roundRobin should also use the information from observatory or burstObservatory. They should only use working servers. This is also an important thing!
Simple things that make life easier... haven't been done. It's a real pity.
I'll have to look at other clients...
Beta Was this translation helpful? Give feedback.
All reactions