and is the same, don't copy (it might not be writeable)
- client: change "result" to "task" in user-visible messages
svn path=/trunk/boinc/; revision=20785
Source of proxy info (descending priority)
- GUI RPC (Manager or boinccmd)
This and only this is saved in state file.
If neither HTTP nor SOCKS server name present,
this is viewed as not present
- environment vars
- cc_config.xml
Show sources of proxy info in message log.
If one is present but overridden, show a message to that effect.
This fixes a bug where someone had a proxy info env var and
forgot about it.
They got an erroneous message saying no proxy was being used.
svn path=/trunk/boinc/; revision=19785
It computed an "overall STD" as the sum of CPU and coprocs,
weighted by the coproc's speed, as we do for LTD.
This was the wrong idea; in the presence of GPUs,
STDs quickly get pushed to +- 1 day and are truncated there.
New scheme: STD is maintained per (resource type, project).
This fixes the above problem,
and it opens to door to round-robin scheduling of GPUs.
- client: the calculation of "anticipated debt" was scaling
by relative resource share.
This wasn't correct, seems to me.
- client: rename "debt" to "long_term_debt" in a few places
(but not in the client state file, for compatibility)
svn path=/trunk/boinc/; revision=19777
<ignore_cuda_dev>n</ignore_cuda_dev>
<ignore_ati_dev>n</ignore_ati_dev>
to ignore (not use) specific NVIDIA or ATI GPUs.
You can ignore more than one.
svn path=/trunk/boinc/; revision=19566
Make them both peak FLOPS,
according to the formula supplied by the manufacturer.
The impact on the client is minor:
- the startup message describing the GPU
- the weight of the resource type in computing long-term debt
On the server, I changed the example app_plan() function
to assume that app FLOPS is 20% of peak FLOPS
(that's about what it is for SETI@home)
svn path=/trunk/boinc/; revision=19310
set a "coproc_missing" flag rather than aborting the job.
If use removes a GPU board while there's a large queue of GPU jobs,
they'll stay queued (until their deadline passes).
Note: this doesn't fix the situation where user connects via
Remote Desktop while GPU jobs are running or queued.
We should check for Remote Desktop every minute or so, and stop GPU jobs.
svn path=/trunk/boinc/; revision=19287
doesn't specify FLOPS for a GPU app,
assume that it runs at CPU peak speed rather than GPU peak speed.
Better to be conservative, otherwise job might be aborted
due to time limit exceeded.
svn path=/trunk/boinc/; revision=19282
and <unsigned_apps_ok> config option.
This tells the client to allow unsigned apps.
For testing.
No file xfers or other network traffic will be allowed if set.
- client: add <exit_after_finish> option (same as cmdline flag)
- client: add <skip_cpu_benchmarks> option (same as cmdline flag)
- client: print message if abort past-deadline unstarted job
- client: improve message when have NVIDIA drivers but no GPU
svn path=/trunk/boinc/; revision=19276
prefs and update, the change wouldn't take effect until client restart.
- client: fix bug in enforcement of "no CPU/NVIDIA/ATI" prefs
svn path=/trunk/boinc/; revision=19236
to accept CPU, NVIDIA and ATI jobs.
These prefs are shown only where relevant:
e.g., only for processor types for which the project has app versions,
and if it has versions for only one type, no pref is shown.
These prefs affect both client and scheduler.
The client won't ask for work for a device blocked by prefs,
and the scheduler won't send it.
This replaces earlier optional project-specific prefs for
"no CPU jobs" and "no GPU jobs".
(However, these prefs continue to be honored on the server side).
- client: if NVIDIA driver is unknown, say that rather than 0
svn path=/trunk/boinc/; revision=19194
"don't use GPUs while computer is in use" to
"don't use GPUs running graphics apps while computer is in use"
for NVIDIA GPUs.
NVIDIA's API for seeing if a GPU is running a graphics app
doesn't seem to reflect GPU use by the OS.
svn path=/trunk/boinc/; revision=19093
1) job finishes
2) job gets marked as "ready to report"
3) scheduler RPC is initiated
Hopefully this won't have an unintended side-effect
svn path=/trunk/boinc/; revision=19051
start only enough jobs to fill CPUs per project,
not all the CPU jobs at once.
I'm not sure how much difference this makes,
but this is how it's supposed to work.
- client: if app_info.xml doesn't specify flops,
use an estimate that takes GPUs into account.
- client: if it's been more than 2 weeks since time stats update,
don't decay on_frac at all.
svn path=/trunk/boinc/; revision=19035
- client: when autoproxy detection is in progress don't attempt to use
old values
- client: user defined proxies should take presidence over automatically
detected ones.
- lib: Re-implement the assignment operator for proxy_info, http_curl.cpp
uses it to clone the proxy information for each http op. See set_proxy();
client/
client_state.cpp
http_curl.cpp
net_stats.cpp
lib/
proxy_info.cpp, .h
svn path=/trunk/boinc/; revision=18971
is running a graphics application.
Change the semantics of the "don't use GPU while computer in use" pref
to "don't use a GPU that's running a graphics app while
computer is in use".
This will increase GPU utilization on multi-GPU systems.
svn path=/trunk/boinc/; revision=18942
This meant that the cmdline args that set config params weren't working:
--allow_multiple_clients
--report_results_immediately
--no_priority_change
--start_delay
svn path=/trunk/boinc/; revision=17741
1) multiply checkpoint period by # of cores (or GPUs)
2) don't write statefile after schedule_cpus()
(we write it after enforce_schedule() if anything
started or stopped, and that's all that matters)
- client: add new log flag <statefile_debug>;
tells you when and why statefile is written
svn path=/trunk/boinc/; revision=17638
Rom Walton