PokingStick(tm) time...

Notes regarding project status and info

4 posts • Page 1 of 1

Postby Dutch » Tue Feb 19, 2019 9:57 pm

Queue stuck at +2000 files, and a small file of mine has been geocoding for several hours... Time to poke the hamsters...

Postby arkasha » Wed Feb 20, 2019 2:31 am

It's not wedged, just heavily utilized. In particular, the WiGLE GeoHamsters trained for average load, and so are lagging behind... But you'll find the maps and stats are updating as you'd expect.

We had a high volume weekend, but we're also busy preparing to release A New Feature... This processing is a necessary step!

Postby pejacoby » Wed Feb 20, 2019 2:39 am

Wowzers, haven't had to PokingStick(tm) the hamsters (thought they were kittens??) in ages!

Would that A New Feature have any sort of a Blue coat?
Image

Postby arkasha » Wed Feb 20, 2019 2:55 am

Well, it's a WiGLE secret, but the kittens handle uploads, and hamsters handle geo-indexing. It turns out that they are much better at geography then cats!

They're partitioned in our infrastructure because cats resent this, and aren't very nice to hamsters as a result.

4 posts • Page 1 of 1

Return to “WiGLE News”

Who is online

Users browsing this forum: Google [Bot] and 1 guest