Indeed we are not able to push continuously to a server - both because
of network availability and also the power consumption is probably
much higher than saving it and sending in bulk.
I think we will indeed aim for the 3 level approach and try to put as
little as possilbe on the main memory just
If Jason's suggestion of pushing it to a server is inadequate, you can
buffer events, and only write them out once a minute or 10 minutes or
something. This will put an upper bound on the number of writes
performed.
You can combine the approaches, and push to the server, and only write
to the file
Why not push the data up to a server?
J
On Apr 4, 2010 2:53 PM, "Nadav" wrote:
Thanks Bob and Dianne,
The issue is that I have no choice but do a lot of writing since this
is a research app that constantly logs phone and user activity over
many months... We are dealing ok with battery and proc
Thanks Bob and Dianne,
The issue is that I have no choice but do a lot of writing since this
is a research app that constantly logs phone and user activity over
many months... We are dealing ok with battery and processing power
(we only write every several minutes), and the main concern remains
t
I've wondered about this, and don't have any definitive answer to
this.
However, there are several factors involved. Flash memory involves
rewriting entire chunks of data, often larger than a single block,
when a single block is written. This can affect how often a given
location is written. Remap
5 matches
Mail list logo
