Hello everyone,
I had an idea concerning a project which contains a pc-based server and some android clients. What i want to try to do is to remove competely the server and get all individual clients to act as servers.
All of these clients are sharing the same database, so the idea is to send to other devices data updated on inserted in any one of them, probably in a cyclical manner.
Now, since these devices will most probably run for at least 16 hours a day, and there will be more than thousand db processes in each one of them having to send them to all other devices, I am wondering whether this would have a large impact on their battery consumption. If, for example, the overhead is less than 20%, it should be acceptable, but if more, I will most probably have to abandon the idea.
Anyone tried something similiar and is willing to provide a report on this subject?
I had an idea concerning a project which contains a pc-based server and some android clients. What i want to try to do is to remove competely the server and get all individual clients to act as servers.
All of these clients are sharing the same database, so the idea is to send to other devices data updated on inserted in any one of them, probably in a cyclical manner.
Now, since these devices will most probably run for at least 16 hours a day, and there will be more than thousand db processes in each one of them having to send them to all other devices, I am wondering whether this would have a large impact on their battery consumption. If, for example, the overhead is less than 20%, it should be acceptable, but if more, I will most probably have to abandon the idea.
Anyone tried something similiar and is willing to provide a report on this subject?