sensorly

Hi everyone, we've started processing the backlog, we're still some days out but the backlog should be processed this weekend at the latest. Our servers are running at peak capacity. Follow status messages here http://status.sensorly.com/ Regarding the site, our site database went down and we couldn't even get to our backups so we got an old backup from 6 months ago and it looks like the geolocation stuff is missing, *sigh* And of course, this is a long bank holiday so there's no one to circumvent the isssue. *sigh* again... The upside to this is that the site is much faster since we moved it to a new much much faster server Thanks for your patience.

That's right : nothing is lost, it's just sitting in a database waiting to be processed. A little more patience and we'll be done

It depends on how long it takes to process the 3 day backlog, my guess is yes.

Ok, so we've safely added 3 servers and wil now decommission 3 servers. I expect updates to resume tomorrow and the 3 day backlog to resorbe within a day or two. Have the maps been loading faster for you since yesterday ?

Ok, I've added it to the code but we're not ready to do a release. I don't think it will be until end of May or June. It would be helpful if you could sign up as a beta tester (email contact@se....lyDOTcom) so you get to test the feature before we release it.

I plan on getting to that next, just need to solve the performance issues first. I've had an idea for this for a while but I haven't tested it yet. Also it would require redrawing everything I'm afraid and that would literaly take weeks for now... we'll see how much faster it could be with the new cluster.

Yup, this upgrade is designed to take care of that too. Thanks for the feedback.

Hi everyone, after much suffering and anguish (hardware issues, network issues, software issues, we had it all...), we're finally in the process of adding capacity to our cluster. We're working on adding 3 servers and the first one is almost completely up to date. Because the servers were so loaded we actually had to stop updating the map for now, don't worry data is stored and will be replayed for updating the map.We should be back online and much faster on Monday. If it's still not fast enough, we're going to add 3 more servers. On another note, we're going to start testing a Content Delivery Network which should speed up the tile loading in the apps too, at the expense of only updating every couple of hours. How soon after collecting data do you typically check the map ? Right now the updates are slow so it's probably hours right ? We may end up having two sources for the map : the CDN (fast but hours to show updates) and the database (slow(er) but shows updates within minutes).

And what exactly would that switch do ?

Ok, will take a look into this. Gotta find what phone reported that data. Any idea of when it was reported by any chance ?

What's the "disable 3G mapping" option ?

We'd mischaracterized 3G speeds and report them as higher than they really are. Lots of people still don't have 4G phones and that would provide them with false info. Perhaps, we would just ask you what type of network the phone is connected to, that would be even easier.

We already do stuff like that on the phone and on the server. Maybe something got through ?

Yes we have cell vs wifi. The thing is, some LTE tests are slow and we don't want to miscategorize those.

Yeah there's a lof of optimization going on to update the maps as fast as possible so zoom levels aren't updated all at the same time. There's no backlog for LTE at the moment.

We'll be adding capacity to our servers in April to bring the update time down.

Exactly, thanks. I'll take a look

Quick update : all of the backlog of data is processed and drawn at least at some zoom levels. Except for 25% of the CDMA data which is 4.5 days late at most. <table border="1" style="font-family: Times;"> <tbody> <tr> <th> Worker</th> <th> Last updated</th> <th> Highest id</th> <th> Time delta</th> </tr> <tr> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.0</td> <td> 2013-03-27 08:22:52.0</td> <td> 54168312</td> <td> 4.48 days</td> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.1</td> <td> 2013-03-27 08:18:08.0</td> <td> 73104784</td> <td> 2 seconds</td> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.2</td> <td> 2013-03-27 08:18:08.0</td> <td> 73104704</td> <td> 4 seconds</td> </tr> <tr> <td> counters.last_reports.CDMA.COVERAGE.3</td> <td> 2013-03-27 08:18:07.0</td> <td> 73104759</td> <td> 2 seconds</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.0</td> <td> 2013-03-27 08:21:31.0</td> <td> 73112429</td> <td> 5 seconds</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.1</td> <td> 2013-03-27 08:21:31.0</td> <td> 73112344</td> <td> 6 seconds</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.2</td> <td> 2013-03-27 08:21:28.0</td> <td> 73112234</td> <td> 5 seconds</td> </tr> <tr> <td> counters.last_reports.GSM.COVERAGE.3</td> <td> 2013-03-27 08:21:31.0</td> <td> 73112334</td> <td> 6 seconds</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.0</td> <td> 2013-03-27 08:21:31.0</td> <td> 73112739</td> <td> 0 seconds</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.1</td> <td> 2013-03-27 08:22:52.0</td> <td> 70917597</td> <td> 12.31 hours</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.2</td> <td> 2013-03-27 08:18:17.0</td> <td> 73105057</td> <td> 3 seconds</td> </tr> <tr> <td> counters.last_reports.LTE.COVERAGE.3</td> <td> 2013-03-27 08:18:15.0</td> <td> 73104961</td> <td> 3 seconds</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.0</td> <td> 2013-03-27 08:18:09.0</td> <td> 73104570</td> <td> 9 seconds</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.1</td> <td> 2013-03-27 08:18:09.0</td> <td> 73104569</td> <td> 9 seconds</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.2</td> <td> 2013-03-27 08:18:09.0</td> <td> 73104562</td> <td> 10 seconds</td> </tr> <tr> <td> counters.last_reports.WIFI.COVERAGE.3</td> <td> 2013-03-27 08:18:08.0</td> <td> 73104564</td> <td> 9 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.0</td> <td> 2013-03-27 08:20:21.0</td> <td> 73109445</td> <td> 0 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.1</td> <td> 2013-03-27 08:20:22.0</td> <td> 73109476</td> <td> 0 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.2</td> <td> 2013-03-27 08:20:21.0</td> <td> 73109445</td> <td> 0 seconds</td> </tr> <tr> <td> counters.last_reports.WIMAX.COVERAGE.3</td> <td> 2013-03-27 08:20:22.0</td> <td> 73109484</td> <td> 0 seconds </td> </tr> </tbody></table>