The queue for refreshing geocache data is unusually long. The servers are working on catching up. Meanwhile our data might not be as fresh as normal.
To be able to write in the forum you need to authenticate. Meanwhile it's read-only.

Change History

New api methods will be announced here. Changes in our data that is relevant to checkers scripts/tags will also be announced here.

Message: Re: Big boring changes incoming (PHP7)

Changed By: arisoft
Change Date: March 09, 2018 04:49PM

Re: Big boring changes incoming (PHP7)
ganja1447 Wrote:
-------------------------------------------------------
> To the above, I did not count your script that's
> slow arisoft
> (https://dev-01.project-gc.com/Challenges//30511).
> Since it works, I didn't see it as priority 1.
> It's still slow though.

Now I have studied this speed problem. My original qguess was right. It is a server side problem.
I made a proof of concept checker https://project-gc.com/Challenges//32341

Live server gives this kind of (debug) results:
Vincenty: 0.02340241 ms 111420.728 m
Haversine: 0.01744844 ms 111195.08 m
Pythagoras: 0.00234117 ms 111420.69881874 m

Dev server gives this kind of results:
Vincenty: 0.155944 ms 111420.728 m
Haversine: 0.127434 ms 111195.08 m
Pythagoras: 0.0019912 ms 111420.69881874 m

Two notes:

- Both Vincenty and Haversine are about 7 times slower in Dev but my own algorithm, which is used in Cache chains, is slightly faster! That explains why Cache chains is not affected by this problem.

- My Pythagoras algorithm seems to be faster and more precise than Haversine ;) but it is usable only up to 100km range.

Original Message

Author: arisoft
Date: March 09, 2018 04:48PM

Re: Big boring changes incoming (PHP7)
ganja1447 Wrote:
-------------------------------------------------------
> To the above, I did not count your script that's
> slow arisoft
> (https://dev-01.project-gc.com/Challenges//30511).
> Since it works, I didn't see it as priority 1.
> It's still slow though.

Now I have studied this speed problem. My original quess was right. It is a server side problem.
I made a proof of concept checker https://project-gc.com/Challenges//32341

Live server gives this kind of (debug) results:
Vincenty: 0.02340241 ms 111420.728 m
Haversine: 0.01744844 ms 111195.08 m
Pythagoras: 0.00234117 ms 111420.69881874 m

Dev server gives this kind of results:
Vincenty: 0.155944 ms 111420.728 m
Haversine: 0.127434 ms 111195.08 m
Pythagoras: 0.0019912 ms 111420.69881874 m

Two notes:

- Both Vincenty and Haversine are about 7 times slower in Dev but my own algorithm, which is used in Cache chains, is slightly faster! That explains why Cache chains is not affected by this problem.

- My Pythagoras algorithm seems to be faster and more precise than Haversine ;) but it is usable only up to 100km range.