Another new one to test. Currently only available for Windows and Mac.

REMINDER TO ALL ALPHA TESTERS:
It's far easier for us to fix problems if you send message logs with the appropriate flags set. The main flags are:

<cpu_sched_debug>: problems involving the choice of applications to run.
<work_fetch_debug>: problems involving work fetch (which projects are asked for work, and how much).
<rr_simulation>: problems involving jobs being run in high-priority mode.

Use these flags from the cc_config.xml file.

Report any problems you get with it to the Alpha email list. This list needs registration.

The un-offical change logs since 6.10.24...

9 December 2009
Charlie
- Mac: Update XCode project for new files cs_proxy.cpp,h, coproc_detect.cpp

13 December 2009
Charlie
- Mac command-line install: add .txt extension to copyright files

14 December 2009
Charlie
- SS: Allow users to set screensaver durations from ss control panel

15 December 2009
Charlie
- Mac SS: In Mac screensaver control panel say "overview screensaver" not "BOINC screensaver"

16 December 2009
Charlie
- Mac Uninstaller: Properly change screensaver settings under OS 10.6

Rom
- client: STD for a device with N instances can increase or decrease at N times real time. My checkin of 7 Dec reflects this by changing the STD limits to +- N*MAX_STD. This looks like a bug to users. Instead, scale that rate of STD change by 1/N, and keep the old limits of +- MAX_STD

- client/manager: first whack at a "snooze GPU" button

- client/manager: finish "snooze GPU" button

- manager: fix bug in the above
- client: deal with situation where GPU has enough RAM to run job, but when we actually run the job not enough GPU RAM is free, so the application fails. This can cause a large number of jobs to fail.
Solution:

* app_plan() can specify the GPU RAM requirements of an app version. This is passed to the client in a new field <gpu_ram> of the <app_version> element.

* prior to starting or restarting a GPU app, the client checks the amount of free RAM on the particular GPU. If it's not enough for the app version, the client doesn't start it, and arranges for the scheduler to ignore it for 5 minutes (by which point there might be more free GPU RAM)

Notes:
1) this change will have effect only when both client and scheduler are updated.

2) the check is done in enforce_schedule(), rather than schedule_cpus(), because only at that point have we assigned a specific GPU to the job.

3) there's another case to deal with: a GPU app's malloc of GPU RAM fails in the middle of the job. Currently the job fails. I plan to add an API call boinc_temporary_exit(x) so that the job can exit and potentially restart in x seconds. (In principle this mechanism is sufficient for all cases, but it could lead to a lot of starting/exiting, so the current change is worthwhile).

- manager: add GPU always/auto/never menu items

- boinccmd: fix output of --get_disk_usage

- manager: bug fixes

- client: maintain mean STD at zero over all projects, not just runnable ones

- client: add an API function boinc_temporary_exit(dt). This exits the app with status zero and no finish file, so the client will restart it. It creates a file "temporary_exit" containing dt. The (new) client reads this file and will postpone scheduling the job again for dt seconds. Old clients will treat it as a premature exit, and potentially try to reschedule the job immediately.

This function is intended for GPU applications that fail to allocate GPU RAM, presumably because a non GPU application has it allocated. We don't want the job to fail, and we want to wait for a while before trying the allocation again.

- client: Fix bugs (indicated by compiler warnings) in recent check-ins. David: please confirm these changes.

- client: ATI: call calShutdown() when done. Otherwise Lenovo can't switch to low-power GPU

- client/manager: show coprocessor short-term debts

- client: fix bug in insufficient video RAM feature

- client: improve CPU sched debug msgs

- client: fix "temporary exit" feature

- client: typo fix

- boinccmd: compile fix

- Cleanup various warnings

- WINSCR: Implement new configuration dialog with new parameters

- WINSCR: Remove crufty code

- WINSCR: Update copyrights in resource files

- Update copyright information

---

BOINC blog

couldn't find it, just the 24.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

couldn't find it, just the 24.

http://boinc.berkeley.edu/dl/?C=M;O=D

Claggy

couldn't find it, just the 24.

http://boinc.berkeley.edu/dl/?C=M;O=D

Claggy

Thanks and I bookmarked the page...boinc_6.10.25_windows_x86_64.exe

---

Official Abuser of Boinc Buttons...
And no good credit hound!

So far so good, install went without a hitch. So I suppose the .24 is no longer needed for testing and the couple using it should goto the .25?

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Only if you like to live dangerously. ;-)

---

Only if you like to live dangerously. ;-)

I once jumped out of a perfectly good airplane.....

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Only if you like to live dangerously. ;-)

I once jumped out of a perfectly good airplane.....

I used to ride motorcycles that had more power than You'd want a noob to have when just starting out(I'm still licensed for motorcycles too).

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Only if you like to live dangerously. ;-)

I once jumped out of a perfectly good airplane.....

I have done that several times, but the planes were always on the ground at the time.

The GPU snooze feature sounds good. On my system with an ati 3850 I'll normally just suspend collatz when I'm watching a movie. Right click & GPU snooze is a lot fewer steps & won't require me remembering to start the project up again. Or if i have fallen asleep watching things....

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Only if you like to live dangerously. ;-)

I once jumped out of a perfectly good airplane.....

I have done that several times, but the planes were always on the ground at the time.
snip

My best friend and I decided to go parachuting...He ended up staying on the ground taking pictures. I think everyone should try it once.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I think everyone should try it once.

If only it would be your last time... ;-)

anyone else notice these development threads never stay on topic?

---

I see someone is useing a version 6.10.3? Didn't see that one in the releases...

cjc_75 20,035.42 389,00
6.10.3 GenuineIntel
Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz [Intel64 Family 6 Model 26 Stepping 4]
(8 processors) NVIDIA GeForce GTX 285 (1024MB) driver: 19107 Microsoft Windows 7
x64 Edition, (06.01.7600.00)

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I see someone is useing a version 6.10.3? Didn't see that one in the releases...

http://boinc.berkeley.edu/dev/forum_thread.php?id=2518&nowrap=true#27054

---

anyone else notice these development threads never stay on topic?

That's crazy talk.

---

me@rescam.org

I think everyone should try it once.

If only it would be your last time... ;-)

anyone else notice these development threads never stay on topic?

wait... there was a topic? oh right... 6.10.25...

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

May be just me but it seems my screen flashes to black when GPU units turn in and hadn't really noticed it doing that much the last few days.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

May be just me but it seems my screen flashes to black when GPU units turn in and hadn't really noticed it doing that much the last few days.

That sounds like perhaps your screen being redrawn was slowed by all the processing your GPUs were/are doing. Is the only recent change the boinc version?

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

please forward this to the Alpha team....

windows xp 64 bit amd phenom II 940. using 6.10.25
boinc and boinc manager processes were using up to 1 core each continuously. reverted back to 6.10.18 no longer a problem

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

May be just me but it seems my screen flashes to black when GPU units turn in and hadn't really noticed it doing that much the last few days.

That sounds like perhaps your screen being redrawn was slowed by all the processing your GPUs were/are doing. Is the only recent change the boinc version?

Yes since I went to 6.10.25 and a while ago I came home and one of my GPU's was at 1 hour and 32 mintes with and hour to go and climbing I shut boinc down and restarted boinc and it finished in a few minutes.

EDIT: When I click on the message tab for a breif second it is still at the last view then it changes, I have never noticed that before. I am doing a bunch of 2 and 3 minute units on my GPU's and my screen flashes every couple minutes no matter what I am doing.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Starting to get some GPU units stacking up again.Have 1 with 00:00 seconds left and another with 00:03 seconds left and a bunch around the 5 minute mark all waiting to run.

---

Official Abuser of Boinc Buttons...
And no good credit hound!