|Anonymous | Login | Signup for a new account||2017-08-21 15:53 UTC|
|My View | View Issues | Change Log | Roadmap | Doomseeker Issue Support Ranking | Rules | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002738||Doomseeker||[All Projects] Suggestion||public||2016-05-20 06:52||2017-07-03 17:37|
|Target Version||Fixed in Version||1.1|
|Summary||0002738: Doomseeker refresh rates are painstakingly slow compared to doomexplorer|
|Description||Now i've been using doomseeker since it came out because one of it's biggest strengths was the refresh rate that at the time was a lot faster than IDE back then. Now not so much anymore.|
RR of the latest DE and DS today:
DE: 2 seconds
DS: 52! seconds for a complete refresh
I think these numbers say enough, Zalewa pls fix
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.
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.|
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.
Commithttps://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.
|Beta update channel is ripe for testing.|
This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.
|Supporters:||No one explicitly supports this issue yet.|
|Opponents:||No one explicitly opposes this issue yet.|
|2016-05-20 06:52||Frits||New Issue|
|2016-05-20 07:25||Dusk||Project||Zandronum => Doomseeker|
|2016-05-21 08:03||Zalewa||Note Added: 0014958|
|2016-05-21 12:49||Frits||Note Added: 0014959|
|2016-05-21 12:50||Frits||Note Edited: 0014959||View Revisions|
|2016-05-21 18:23||AlexMax||Note Added: 0014964|
|2017-02-28 20:30||Zalewa||Status||new => acknowledged|
|2017-03-04 13:12||Zalewa||Note Added: 0016928|
|2017-03-04 13:12||Zalewa||Assigned To||=> Zalewa|
|2017-03-04 13:12||Zalewa||Status||acknowledged => needs review|
|2017-03-04 13:39||Zalewa||Note Added: 0016929|
|2017-03-04 13:39||Zalewa||Status||needs review => needs testing|
|2017-07-03 17:37||Zalewa||Status||needs testing => resolved|
|2017-07-03 17:37||Zalewa||Fixed in Version||=> 1.1|
|2017-07-03 17:37||Zalewa||Resolution||open => fixed|
Questions or other issues? Contact Us.
|Copyright © 2000 - 2017 MantisBT Team|