1) Message boards : BOINC client : BOINC is NOT robust against BSOD / lockups (Message 2819) Posted 28 Jan 2006 by GreatInca Post: X-Plane (8.32 this time) BSOD on the video driver (nv4disp), instead of locking up on the machine. Seems to be about twice a week. the BSOD took out most of BOINC's setings and SETI is back to the currupt banner.jpg thing and LHC's .exe is missing and both LHC and einstein did resets. I managed to get my LHC work copied. BOINC seems to leave the orphaned work in the directories. I found 3 orphaned CPDN workunits. Is there any way I can get these reconnected? and can the dev people make BOINC more robust against hard crashes by bad games and buggy video drivers?

2) Message boards : BOINC client : BOINC is doing only LHC which I have set at 125 (12.5%) (Message 1380) Posted 30 Nov 2005 by GreatInca Post: SETIClassic burns through 18-24 workunits per day. Its about 5 days total. LHC has 12 workunits plus the 2 its working on and is taking about 5 hours per unit, 2 at a time (2 get completed every 5 hours). There are no download dates in the work tab. It hasn't downloaded any new work units yet (according to the messages tab). I'm getting my alienware laptop back on friday. It has an identical processor and it is 90% as fast (crunching seti) as the desktop. Its SETICommander has over 300 workunits in the cache because I export workunits to my 2 older computers that are not on the internet (6-8 and 3-4 work units per day). I also stashed 999 workunits onto a laptop i gave to my mom. I'm guessing they're going to be wasted as i'll see her again next summer. She's not very computer litterate. That machine does about 3 work units per day.

3) Message boards : BOINC client : BOINC is doing only LHC which I have set at 125 (12.5%) (Message 1363) Posted 30 Nov 2005 by GreatInca Post: I think LHC would be much cooler if it were for crunching actual atom smashing footage (figure out the guts of the universe from bashing very little particle things). I would do LHC 500 SETI 250 Einstein 125 Climate 63 and some other one 62 if that were the case. But optimizing a topnotch particle accelerator's reliability is cool too, so i picked it as a project, but i wasn't expecting the deadline sensitive behavior. I relize the LHC monopoly is from the tight deadline combined with the large cache setting (7 days) and the default equal priorities that you can't change upon first attatching to the project, so it downloaded too much work for the given deadline and desired priority settings and it is prioritiezing the deadline. I still say screw the dealine sensitivity. There are plenty of other non overdue workunits to get credit for, and I still would like 50% on a 2 (virtual) processor system to mean go hog a CPU just for it (same for 25% on a 4 CPU system). Oh yeah another idea for improvement that might m ake it more optimal to run two workunits of one project over an workunits of 2 separate projects is to have one instance process two workunits on two separate threads instead of running 2 instances of the project app (sunch as sixtrack___*.exe). The OS is smart enought to put the separate intra-application threads on sepearate processors even if it is just virtual dual-ALU single processor (or both for dual-core, hyperthreaded making 4 virtual CPUs in 1). That may help L1/L2 cache utilization and make my idea of 50% prio means hog a core no longer any good.

4) Message boards : BOINC client : BOINC is doing only LHC which I have set at 125 (12.5%) (Message 1360) Posted 30 Nov 2005 by GreatInca Post: OK I hope BOINC's weightings are longterm. I wanted SETI to get exclusive use of 1 CPUCore and The rest to share the 2nd (50/25/25). If SETI runs out of stuff and the server is broken then Einstein gets to monopoize a CPU while LHC/Climate shares the 2nd 50/50. Definitly looks like it don't work work that way.

5) Message boards : BOINC client : BOINC is doing only LHC which I have set at 125 (12.5%) (Message 1358) Posted 30 Nov 2005 by GreatInca Post: BOINC is getting all the CPU, SETI Classic (via SetiCommander) is getting 0. If i set SetiCommander to run SetiClassic at 'Normal' then Seticlassic gets most, leaving about 5-10% for BOINC. I would like BOINC and SETIClassic to share nice but SetiCommander low is probably '2' and BOINC low is '3' on the system priority. The PC is a Alienware Pentium4 3.4GHZ HT. I could care less for the deadline. Better late than not at all. Why set such a close deadline to exploit the 'earliest deadline first' mode to cheat out more CPU from clients regardless of settings? At least it doesn't seem to download any more LHC workunits. Maybe the 100 default priority number made it download too much work? I did set the cache size to 7 days (the connect every 'x' days setting) on the inital config webform. Maybe if the share priority number was added to the initial join project web form? I think it would be even better to move the CPU share priority local. I'll just turn BOINC off until SETICommander clears out its cache. It still has 105 SETI Workunits in cache (send 16 at a time, recieve 32 at a time, 128 cache size). I told SetiCommander to not download more workunits for SETIClassic.

6) Message boards : BOINC client : BOINC is doing only LHC which I have set at 125 (12.5%) (Message 1350) Posted 30 Nov 2005 by GreatInca Post: Its the other away around. I keep seti classic so some SETI will still get done, but it don't work because BOINC is getting all the CPU. BOINC is still doing LHC exclusively, even into today.

7) Message boards : BOINC client : BOINC is doing only LHC which I have set at 125 (12.5%) (Message 1321) Posted 30 Nov 2005 by GreatInca Post: So much for running SetiCommander in addition to BOINC. BOINC's low priority seems to be higher than SETI@Home's low priority and it won't let me change it in task manager for either. Access denied for BOINC, SetiCommander changes the Seti@Home client Prio back to low and you can only choose between low and normal in SetiCommander (I prefer Below-Normal or the same 'Low' between the two). I installed BOINC as a service running under the local system account.

8) Message boards : BOINC client : BOINC is doing only LHC which I have set at 125 (12.5%) (Message 1320) Posted 30 Nov 2005 by GreatInca Post: It seemed to have downloaded an equal amount of work for all projects. LHC's deadline is 12/3. SETI and Einst3ein is 12/13. It has been running LHC work exclusivly all day. Client version is 5.2.13 . ClimatePrediction finally downloaded work, a very large workunit with a deadline of sometime next year. I'm running my old SETI Client to force its 50% share. I just migrated from SETI classic this morning.

9) Message boards : BOINC client : BOINC is doing only LHC which I have set at 125 (12.5%) (Message 1313) Posted 29 Nov 2005 by GreatInca Post: SETI is 500 (50%) Einstein 250 (25%) LHC 125 (12.5%) ClimatePrediction 125 (12.5%) Its doing only LHC and it obviously has cached work for SETI and Einstein. ClimatePrediction seems to be broken for some reason.

---

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.