Dear all, I'd like to hear comments on the following problem/idea:
For Android on ARM, we at E@H have optimised our science app to require less RAM than our regular CPU app versions for x86 CPUs. OTOH, we would like to have only one application (in the BOINC terminology) for all CPU platforms, so only one suite of work generators, validators etc is needed and x86 and ARM app versions get the same tasks and can even cross-validate against each other, which we think is good. But as the memory requirements are associated to the work unit, we have to use the maximum value for all the different app versions/ plan classes. IMHO the situation is somewhat similar to the execution speed differences for different plan classes that cannot be fully modelled by the BOINC benchmark results (e.g. for CPU-GPU comparison) and I understand that the solution for this was a scaling factor that can be configured with plan classes to let the scheduler know that results are computed faster by a certain factor for a particular plan class compared to what BOINC would assume otherwise. Would it be feasible/a good idea to also have a configurable scaling factor for RAM requirements, perhaps ?? I think many projects will find that optimising for RAM size is important for Android. Cheers HB ----------------------------------------------------------------- Heinz-Bernd Eggenstein Max Planck Institute for Gravitational Physics Callinstrasse 38 D-30167 Hannover, Germany Tel.: +49-511-762-19466 (Room 037) _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
