I still have the same problem I did with the 5.9.x versions (the BOINC manager closses on its own and my computer goes to a blank screen which I have to open the task manager to exit). But I now know this has nothing to do with the screensaver and it only happens when I run BOINC alpha.

My computer runs windows XP home with sp2

---

Check out the forum for Canada the #1 Canadian team.

There was a thread over at Seti about the dual core benchmark issue a few months ago.

I believe there's a trac ticket open on it as well.

The developers are aware of it as there was also a discussion on the alpha list around the same time as the Seti thread.

Give me a bit and I'll dig up the Seti thread and the Trac ticket.

Seti Thread

---

Kathryn :o)

I just submitted the benchmarks issue into Trac as Ticket #228. Please add any data you have on the issue. Trac requires separate registration. Please include the start-up messages from BOINC as well as OS and how you installed BOINC (single/shared/service).

---

Kathryn :o)

Just couple of small problems with 5.10.0 version

- It doesn't remember any alterations to column widths when you restart it, which means that you can't see the Status column if you don't have the window maximised.

- On "snooze" it just went ahead and finished an Xtremlab unit I was crunching at the time (could be an Xtremlab problem, but I haven't noticed it on previous versions of BOINC Manager)

Still, in view of the benchnarking problems, I'll go back to the previous version anyway...

---

I still have the same problem I did with the 5.9.x versions (the BOINC manager closses on its own and my computer goes to a blank screen which I have to open the task manager to exit). But I now know this has nothing to do with the screensaver and it only happens when I run BOINC alpha.

My computer runs windows XP home with sp2

I used to run the latest test project on three machines. I went back to the stable manager 5.8.16 and ran BOINC Alpha and I had no problems at all. So there is an issue with 5.9.x and 5.10.x running Boinc Alpha because I had the problem on all three machines while running the test managers.

---

Check out the forum for Canada the #1 Canadian team.

I still have the same problem I did with the 5.9.x versions (the BOINC manager closses on its own and my computer goes to a blank screen which I have to open the task manager to exit). But I now know this has nothing to do with the screensaver and it only happens when I run BOINC alpha.

My computer runs windows XP home with sp2

I used to run the latest test project on three machines. I went back to the stable manager 5.8.16 and ran BOINC Alpha and I had no problems at all. So there is an issue with 5.9.x and 5.10.x running Boinc Alpha because I had the problem on all three machines while running the test managers.

Grizz...

You really need to sign up for the alpha list and report it there. The developers don't read these boards unless we point them here for problems with the release versions that the volunteers can't solve.

The list is where all the discussion and bug hunting goes on. The alpha boards are rarely used as well.

---

Kathryn :o)

Please include your OS and CPU info in your posts. I may help to diagnose the issues.

I just submitted the benchmarks issue into Trac as Ticket #228. Please add any data you have on the issue. Trac requires separate registration. Please include the start-up messages from BOINC as well as OS and how you installed BOINC (single/shared/service).

David just checked in a fix for this.

Author: boincadm
Date: 2007-06-03 13:13:38 -0700 (Sun, 03 Jun 2007)
New Revision: 12808

Modified:
  trunk/boinc/checkin_notes
  trunk/boinc/client/cs_benchmark.C
Log:
   - client: fix inconsistent integer benchmarks on Windows
       with multicore machines.  I don't know why this happened,
       but I fixed it by doing integer benchmarks only on CPU zero.
       This is OK since cores have separate integer units
       (but not necessarily FP units)

   client/
       cs_benchmark.C

---

Kathryn :o)

OK --

Working on a PC with XP Home for an OS
x86-based PC
x86 family 15 model 47 stepping 2 AMD
1024mb total physical memory
2.00gb total virtual memory
1.96gb avail virtual memory
2.33gb page file space

I'm currently using ver. 5.10.5 of BOINC, with a shift every 60 minutes.

My question is related to those of us who have several projects running in tandem on one computer. There are times when my system is bloated with several projects that have work which has reached the 90%+ state, and due to the 60 minute shift rule, they are left hanging for 6-8 hours until that project is again enabled. Is there a way to add a step in the BOINC manager that would look at the percent complete and the time to go fields, and if the percentage was 90% or greater, and the time to complete that specific project was less than the shift time (e.g. 60 min on my machine), that BOINC would hold that project to completion before the shift? It would seem to make the throughput a little bit more efficient.

Just a suggestion ...

---

If I've lived this long, I gotta be that old

My question is related to those of us who have several projects running in tandem on one computer. There are times when my system is bloated with several projects that have work which has reached the 90%+ state, and due to the 60 minute shift rule, they are left hanging for 6-8 hours until that project is again enabled. Is there a way to add a step in the BOINC manager that would look at the percent complete and the time to go fields, and if the percentage was 90% or greater, and the time to complete that specific project was less than the shift time (e.g. 60 min on my machine), that BOINC would hold that project to completion before the shift? It would seem to make the throughput a little bit more efficient.

Just a suggestion ...

This has been suggested before. Since there are several projects that have bad time estimates and/or sit at/near 100% for long times it was decided against trying to impelement it. There are also projects that exceed 100% complete to make this more problematic.

---

BOINC WIKI

BOINCing since 2002/12/8

I had the KWSN 2.2B optimized apps running on 5.8.16.
Updated to 5.9.x no problem
Updated to 5.10.4. The task tab hung the app.

The only way to restore functionallity (any version) is uninstall, delete the directory and reinstall without the opt apps.

Don't try KWSN and 5.10.4

I still have the same problem I did with the 5.9.x versions (the BOINC manager closses on its own and my computer goes to a blank screen which I have to open the task manager to exit). But I now know this has nothing to do with the screensaver and it only happens when I run BOINC alpha.

My computer runs windows XP home with sp2

I used to run the latest test project on three machines. I went back to the stable manager 5.8.16 and ran BOINC Alpha and I had no problems at all. So there is an issue with 5.9.x and 5.10.x running Boinc Alpha because I had the problem on all three machines while running the test managers.

Grizz...

You really need to sign up for the alpha list and report it there. The developers don't read these boards unless we point them here for problems with the release versions that the volunteers can't solve.

The list is where all the discussion and bug hunting goes on. The alpha boards are rarely used as well.

Hi all,
Noob here, going to do testing on gutsy as want to have a stable 5.10 soon. Can u either pm me or tell on the board where the list is?

http://boinc.berkeley.edu/email_lists.php shows only 8 lists & I did read the foot-note which does tells about the blacklist (spam) perhaps that's why its not listed.

It is listed on http://www.ssl.berkeley.edu/mailman/listinfo

---

I had the KWSN 2.2B optimized apps running on 5.8.16.
Updated to 5.9.x no problem
Updated to 5.10.4. The task tab hung the app.

The only way to restore functionallity (any version) is uninstall, delete the directory and reinstall without the opt apps.

Don't try KWSN and 5.10.4

You have to modify the app_info.xml and remove ALL references to versions not 5.15

> received batch of 8 with same due date well into the future.
> When it got to the 1st, it tried it for a minute and moved to the next,
> 1 minute or so and the next, until it done all 8, after which it
> reverted to the 5th in the task buffer and continued on that one

I've seen that also. I enabled cpu_sched_debug which reports that
the specific project had projected deadline misses.

Deadline misses are easy to have cpu_efficiency=0.86 (less if you were playing games) times project share % can easily calculate completion date out beyond the deadline.

Normally it would start one of the WU with earliest deadline and smallest To Complete estimate and continue until complete.

However. If the project's duration_correction_factor is too low then after several minutes the To Complete estimate will increase. The other WU have a smaller To Complete and BOINC switches. The DCF doesn't get updated until a WU finishes.

Why not crunch 24/7 with cpu usage set to 75% for the heat.
Set connects every N days to a realistic value (.1=always online, 2=dial up.) If it was larger because you wanted extra in the cache set the Maintain enough work for an additional N days (Requires 5.10+ client.)