As I stated before someone needs to explain how the client interacts with the server. This upload issue Paladin* is talking about always was eon issue from long time ago. eOn is that kind of project that needs permanent internet connection and increases bandwidth and slowdowns internet connection when surfing. When you have two or three machines running eOn you can start to feel your internet connection going down, imagine when you have above 5 machines. My connection is an ADSL one: 24Mb download speed, 1Mb upload speed.
This issue will increase its effect by the growth of the project. To minimize it the wu's should be longer to process.
In our simulations we need to perform work (saddle searches) for the current configuration of the chemical system in order to find what processes (events that change the configuration of the system such as an atom hopping on a surface) are available. Once we have done enough searches to meet our confidence goal we choose one of these processes and advance to a new state. Once we are in a new state no more saddle searches need to be done for the previous state. The work units are these saddle searches that we need to do some number of on average. This means that work units, in order to be useful, must be completed in about the amount of time it takes for us to complete all of these searches.
Currently for the systems we are studying and the potentials we are using a single saddle search takes less than a minute and we are making each work unit do 10-50 saddle searches. Each saddle search produces the same amount of data. Simply making each work unit take longer by doing more saddle searches will have two effects. First, the work unit results will be that much larger to upload (since the files grow linearly with the number of searches we do). Secondly, we will get our searches back in even bigger chunks. We might only need to do several thousand searches per state, which means for a given simulation (of which we run more than one at a time on BOINC) we never need more than several thousand searches being performed at once. This means that we would like to keep the number of saddle searches small in order to more efficiently parallelize the problem.
Another way of making work units take longer is to use more accurate potentials. The potential is the way the energy and forces in the chemical system are calculated. Right now we are using a very simple one which is why a single saddle searche take less than a minute. We hope to use more accurate ones soon, where one search might take many minutes or hours while still producing the same amount of output as our searches that currently take seconds. This would mean that one workunit would equal one search, which is very little data compared to the current work units and take much longer. These types of work units are better suited to distributed computing.
However, currently I plan on implementing the server and client side compression to help this issue somewhat.