|
Notes |
|
|
(0014958)
|
|
Zalewa
|
|
2016-05-21 08:03
|
|
Refresh speed is configurable in configuration box on the "Query" page. Please try adjusting your settings.
We go for the safe option for a reason that I have noticed that some routers like to "block" the traffic if they notice you rapidly "spam" numerous IP addresses with UDP packets. Doomseeker was not working for some people. |
|
|
|
(0014959)
|
|
Frits
|
2016-05-21 12:49
(edited on: 2016-05-21 12:50) |
|
Tested it with agressive which still took 25 seconds. Still ages of time compared to DE.
Then modified the values to be as low as possible which reduced it down to 10 but as you said made some servers "block" my refresh on more attempts.
Surely you can squeeze some more out of it? How does DE do it in 2 seconds without ever failing?
|
|
|
|
|
|
It might be useful to use Wireshark to dump a capture of Doom Explorer querying servers compared to Doomseeker. Maybe it's doing a non-obvious trick. |
|
|
|
(0016928)
|
|
Zalewa
|
|
2017-03-04 13:12
|
|
It turns out the special thing that Doom Explorer is doing is not pushing all queries through a single socket but having 1 socket per 100 servers. This prevents the problem of query replies becoming lost.
Commit'https://bitbucket.org/Doomseeker/doomseeker/commits/7aacc1d0113564e7183943639434a9a4ec144f69 [^]' implements the same mechanism for Doomseeker and also reduces limits imposed on Query speed setting. A "Very Aggressive" query preset has also been added, with which I can achieve 3 seconds refreshes for ALL of the supported ports. |
|
|
|
(0016929)
|
|
Zalewa
|
|
2017-03-04 13:39
|
|
|
Beta update channel is ripe for testing. |
|