Good point. The DB size issue isn't disk space, but rather that (at least on SETI@home) the server runs well only if the DB fits into RAM.
-- David On 23-Aug-2013 6:12 AM, Jon Sonntag wrote:
If not in the database, the 1024 characters of CPU info gets sent every single time the host contacts the server using network bandwidth over and over and over and over and over and over.... What costs more, a GB of disk space or a GB of bandwidth? (Hint: It isn't disk space.) Jon Sonntag On Thu, Aug 22, 2013 at 7:08 PM, David Anderson <[email protected] <mailto:[email protected]>> wrote: We could do this, but it would require adding a 1024-character field to the host DB table, which would increase the DB size somewhat (e.g. by 1 GB for projects w/ 1M hosts). Probably not worth it. On 22-Aug-2013 3:14 PM, Carl Christensen wrote: it might be nice on the boinc project's web page for computer (as Bernd mentioned) to print the p_feature field (like we do for bencharks)? plus the "coprocessor" line I was thinking "ARM Neon" & VFP counted as a coprocessor (FPU rather than GPU)! ;-) _________________________________________________ boinc_dev mailing list [email protected] <mailto:[email protected]> http://lists.ssl.berkeley.edu/__mailman/listinfo/boinc_dev <http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev> To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _________________________________________________ boinc_dev mailing list [email protected] <mailto:[email protected]> http://lists.ssl.berkeley.edu/__mailman/listinfo/boinc_dev <http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev> To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
_______________________________________________ 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.
