On Tue, Jul 23, 2013 at 4:54 AM, Heinz-Bernd Eggenstein <[email protected]> wrote: > 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. > >[...] > > 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.
The way we did this for SETI@home was to make the app on all platforms able to run in the same minimum amount of memory, and the use the value of app_init_data.host_info.m_nbytes (you could divide that by app_init_data.host_info.p_ncpus) to decide whether to allocate more memory. I believe that BOINC does not kill apps for exceeding the memory bound, so this is, in theory, acceptable. It can potentially cause problems on non-virutal memory systems because BOINC is using the memory bound as an estimate of memory usage. _______________________________________________ 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.
