Changes between Version 7 and Version 8 of DevProjects

Timestamp:

Jul 13, 2007, 1:39:17 PM (17 years ago)

Author:

davea

Comment:

--

DevProjects

@@ -12 +12 @@
           * Write an example compound application (and suggest API revisions to make this easier).
           * Create Makefiles and project files to build the sample applications using MinGW and DevC++.
-          * Extend wrapper application handle multiple tasks, and test/debug it.
           * Investigate the crlibm library for generating identical results across processors (or at least reducing the number of cases for HR).
           * Graphics in separate program.
@@ -31 +30 @@
           * Don't enforce RAM limits unless free RAM is low
           * Extend general preferences to allow users to specify different time-of-day restrictions for different days of the week.
-          * Write a simulator for the CPU scheduler and work fetch policies (Derrick Kondo is working on this).
           * Log result start/ends (for use by 3rd-party software like BoincView).
           * Prevent disk space usage from exceeding user preferences, and enforce resource shares, with file deletion according to project policy.
@@ -42 +40 @@
           * If using an AMS, put link to AMS (or user page) in sys tray popup, elsewhere
           * Properties pages for projects, jobs
-          * Project list (Rom's working on this)
           * Turn off alerts (Rom's working on this)
           * Have the Manager do RPCs in a separate thread.
     * Server/Back End:
-          * Add a 'validity' field to host. Exponential average of fraction of valid results. Demand more replicas if some are from suspect hosts.
-          * Allow the scheduler to take a list of platforms (not just one). E.g. a Win64 machine could send Win64 and Win32.
           * When using HR, if the scheduler has sent one result of a WU using a particular app version, it should use the same app version for other results from that WU. Need to change protocol to specify version num; need to change client to use this.
           * Implement a mechanism so that server software detects incompatible database format
           * Scheduler: implement mechanisms so that server:
-                * Sends only results likely to finish by their deadline
-                * Sends commands to abort results that can't get credit
-                * Sends commands to recommend abort of results that may get credit, but are not useful (i.e. canonical result already found)
                 * Attempts to send results from the same WU to hosts with similar speed, so that a fast host doesn't have to wait weeks to get credit. 
           * Implement a 'benchmark result' mechanism: every host runs a benchmark result per app version, and the CPU time determines credit/CPU for future results 
@@ -66 +58 @@
           * Change the ops/ web pages to require login by a user with admin privileges.
           * Add 'referral' mechanism: new user creates account, enters email of 'referrer' (or goes to URL that has it embedded). Give referrer a fraction of credit (or a 1-time bonus). List referrals on user page (show only those still active). Add new referral table to DB.
-          * Add supported platforms, other info to get_project_config.php
           * Make it easy for teams to offer a client download that features their skin, and pre-register the user on that team for any projects he attaches to.
           * Change default Q&A page to refer BOINC-specific questions to BOINC web site