I am looking at trying to get the Flukso to talk over 3G mobile wireless and have been looking at the amount of data that is being sent.
It appears that the device is consuming about 1KB per minute in data - or 43M per month.
The surprising things was that 67% was in received data and only 33% was transmitted data. I was expecting the ratio to be 1:100 rather 2:1. And also much much less data being sent.
Is this consistent with what other people are getting?
Given this is a 3G connection and very expensive, I would like to try and limit the amount of data while maximising the number of data polls.
At the moment, the measurements are taken every 5 minutes.
Does anyone know if there are any other things that influence the traffic other than just the flukso service?
How do you measure the usage? is that form the Mobile operator invoice?
It could be that your mobile operator is havin a 1kb or 10kb minimal unit for a data counting and thats why it turns out this way.
Well, there's the SSL session overhead for each batch of POSTs to the server every 5min. In parallel there's a heartbeat call every hour, but traffic-wise that should be negligible.
There's currently no gzip compression in upstream, but since the payloads are typically small, the gain through compression will be minor.
I guess the HTTP header overhead will be the main culprit, which is not compressed for HTTP. Unless we start using Google's SPDY.