Changes between Version 6 and Version 7 of AppMultiThread


Ignore:
Timestamp:
Nov 20, 2007, 3:44:31 PM (17 years ago)
Author:
Nicolas
Comment:

Comment. Please don't kill me.

Legend:

Unmodified
Added
Removed
Modified
  • AppMultiThread

    v6 v7  
    6767 * app->core (process control channel): {{{<actual_nthreads>}}}
    6868
     69{{{
     70#!comment
     71
     72*ahem*
     73
     74Unless, before we get to add multi-threading support, we do the sane thing and change the communication use a compact binary protocol over a pipe instead of XML over shared memory.
     75
     76"shared memory has to be right below 'printing and scanning with OCR' in terms of favorite means of IPC" -- rtyler on #boinc, irc.freenode.net
     77
     78By the way, it would be nice to stabilize the API documented here, and implement it as a stub that always tells the app to use 1 thread. That way project developers don't have to wait for BOINC support before making multi-threaded applications. They could create apps supporting multiple threads right now, and whenever the BOINC client (or an unofficial fork, since everything will be so nicely documented, right?) adds support for this, they would Just Work(tm).
     79}}}
     80
    6981Client maintains estimates of CPU efficiency per job,
    7082uses this to scale {{{target_nthreads}}}.
    71 
    7283
    7384Implementation ({{{enforce_schedule()}}}):