Posts by Keck_Komputers

1) Message boards : Questions and problems : different project / core (Message 23623)
Posted 11 Mar 2009 by Keck_Komputers
Post:
The 6.6.x version should do a better job of scheduling the GPU. However there will still be the possibility of both CPUs running the same project.
2) Message boards : Questions and problems : Seti@home working on 2 pieces at the same time (Message 22964)
Posted 9 Feb 2009 by Keck_Komputers
Post:
Having 2 tasks should not interfer with the screensaver, we need to look for some other reason for the screensaver problem.
3) Message boards : Questions and problems : BOINC 6, 2 questions (Message 22408)
Posted 13 Jan 2009 by Keck_Komputers
Post:
You do not have to edit the registry to stop BOINC manager from starting. In the advanced view under the advanced tab there is a checkbox for running the manager at startup. Still more cumbersome than I would like but not as bad as digging in the registry.
4) Message boards : BOINC client : Reboot problem (Message 21961)
Posted 21 Dec 2008 by Keck_Komputers
Post:
There should be a file called something like reboot_pending in your BOINC data directory. Delete this file and you will no longer been asked to reboot.
5) Message boards : Questions and problems : How many different projects BOINC can schedule to run simultaneously? (Message 21733)
Posted 11 Dec 2008 by Keck_Komputers
Post:
The CUDA tasks also need some CPU time, 40% of a core for SETI. So you may see varying numbers of CPU tasks running. I would expect the norm to be 3 + 1 for a quad.
6) Message boards : BOINC client : bug in idle detection (Message 21703)
Posted 10 Dec 2008 by Keck_Komputers
Post:
I think not using load level detection was a design decision more than anything else. BOINC is designed to make the load level 100% in normal situations so that could be a conflict. Also I don't think windows differentiates between normal processes and "nice" processes like *nix does so any kind of load level detection would cause problems in windows.
7) Message boards : Questions and problems : Connecting to Local Host - Connection Failed (Message 21701)
Posted 10 Dec 2008 by Keck_Komputers
Post:
You should update your BOINC anyway as the client you are using now doesn't do FLOP counting as the 5.10 and 6.2 clients do. This means that it is possible that you are requesting for and getting zero credits on Seti, giving your wingman zero credits as well.

Upgrading to a newer client should be painless. Read this FAQ and keep a good eye out in the 6.2 installer for the Advanced button in case you don't want to install the new version as a service.

BOINC 6.2 should install directly over 4.45, it should uninstall the older version if there are no corruptions of the older software's uninstaller. In any case, it should keep you attached to your projects. Do keep in mind that you'll need a reboot, or at least a log off/log on for the changes to catch on.

And if you have any questions or problems, just post about them, or look in the BOINC FAQs.


I think the version 4 clients are old enough that they have to be unistalled before a new one can be installed, but other than that Ageless is correct.
8) Message boards : BOINC client : bug in idle detection (Message 21677)
Posted 8 Dec 2008 by Keck_Komputers
Post:
KILLing BOINC processes will most likely cause the task to error out. A better way would be using "boinccmd --set_run_mode never" to pause and "boinccmd --set_run_mode auto" to resume in your script. more details

Coming in 6.4.x you will be able to define exclusive apps that when running will cause BOINC to suspend processing.
9) Message boards : BOINC client : 64-bit projects (Message 21535)
Posted 27 Nov 2008 by Keck_Komputers
Post:
http://boincstats.com/forum/forum_thread.php?id=1774
This thread lists which projects have 64bit clients. However most of them it makes little difference compared to the 32bit client. ABC, APS and primegrid are the exceptions where there is a substantial advantage to use the 64bit client.
10) Message boards : Questions and problems : Can't seem to stay attached to new projects. (Message 21513)
Posted 25 Nov 2008 by Keck_Komputers
Post:
Attaching a new host by default will not attach an existing host to a new project. You can attach existing hosts to new projects using either the host list or the resource page.
11) Message boards : Server programs : Won't finish in time ... (Message 21320)
Posted 18 Nov 2008 by Keck_Komputers
Post:
p.p.s.: The concept of Long Term Debts is a mess anyway (especially in combination with CPDN), I have a workaround for it though, that resets all values to 0 on a client restart.


That fails to respect your resource shares. A better solution would be to add code to the scheduler (or some other module) that diagnoses the situation and prescribes corrective actions to the user. The corrective actions would be to either:

1) reduce the resource shares for projects which cannot supply enough work to meet the shares, or
2) detach from the project, or
3) reset the debts

Reseting the debts on EVERY client restart is not a good idea when users are attached to projects that DO supply enough work to meet their shares.

The concept of Long Term Debts is sound as long as you attach to projects that can provide enough work to meet your resource shares. The scheduler attempts to respect shares that simply cannot be met. In other words it attempts to do the impossible in certain combinations of projects and shares. It cannot do the impossible so why not just have the software tell the user like "this cannot work, you need to make some adjustments". THAT would be sane. Attempting to do the impossible over and over and over every friggin day is NOT sane.

Easy to say, probably not so easy to code it. And I don't know how CPDN affects it, just some thoughts, FWIW.


That won't work either. It ignores or abuses the participants that want to run 50 projects on a 500mhz CPU. In that case there is no way to respect the resource shares in a short time. It may take years to balance even with short tasks and long deadlines. The current system is not perfect however I have yet to see an alternative suggestion that is as good at handling all possible cases.
12) Message boards : BOINC client : Hyperthreading / SMT support (Message 21311)
Posted 18 Nov 2008 by Keck_Komputers
Post:
You can set BOINC to only use half of your CPUs, but you can not control which CPU(s) it runs on.
13) Message boards : Questions and problems : Changes in 6.2.15 from 6.2.14 (Message 21267)
Posted 15 Nov 2008 by Keck_Komputers
Post:
There will probably be another silent upgrade soon as well. The WCG test version is up to 6.2.27 when they get their version released the standard version will probably be bumped to match.
14) Message boards : BOINC client : GPUgrid polluting CPU statistics? (Message 21150)
Posted 6 Nov 2008 by Keck_Komputers
Post:
Yep. All stats are credited to the host involved. That stat page just associates the host with the reported CPU. I suppose we will have to see about getting other computing resources added to the host data records.
15) Message boards : BOINC client : Are you planning BOINC with GPU support? (Message 21036)
Posted 29 Oct 2008 by Keck_Komputers
Post:
EDIT: oops, did not see the date there... got here from google and resurrected a 2 year old thread, sorry.

In the mean time, the next upcoming BOINC 6.4 has GPU support. Thus far only for nVidia GPUs; ATI support will follow.

It is still up to the individual projects to make use of the GPU and other computing resources. The 6.4.x client will just make it easier for them and adds some more intelligent scheduling.
16) Message boards : Questions and problems : Preferences enhancement request (Message 20660)
Posted 4 Oct 2008 by Keck_Komputers
Post:
There is a web based project preference to allow different apps. This is not quite what you are asking but may help. You can set it to not get tasks for a specific app.
17) Message boards : Questions and problems : Multiple Name Problem (Message 20355)
Posted 19 Sep 2008 by Keck_Komputers
Post:
You need to have a path that includes all servers and clients. The simplest way to accomplish this is to have on computer attached to all of your accounts. You can attach PS3grid to any type of host, however they will not provide work to most platforms.
18) Message boards : Questions and problems : Isn't it a shame that BOINC isn't multithreaded (Message 20232)
Posted 13 Sep 2008 by Keck_Komputers
Post:
Multi-threading support is already in the version 6 clients (improvements due in 6.4.x). However none of the projects have a multi-threaded application yet.
19) Message boards : Questions and problems : Graficos - Graphics (Message 20190)
Posted 12 Sep 2008 by Keck_Komputers
Post:
LHC does not have a v6 compatible application yet.
20) Message boards : Questions and problems : Question about CPU Usage percentage (Message 19720)
Posted 23 Aug 2008 by Keck_Komputers
Post:
The CPU Usage function is a thermal throttle. As far as I know it has no integration into the work-fetch policy module of BOINC. Perhaps that eventually, after long enough use, that you'll see work-fetch decrease, but not from minute one.

It takes about a month for the work-fetch policy to adjust for throttling. It should make your % that BOINC is allowed to work drop down to approximately match the throttle setting. That will reduce the work fetch.

Is this advice based on latest clients or from longer past? I use Threadmaster GUI at 70% this moment on a quad and the DCF hiked to 1.44 rather rapidly and is staying in that area (Coincidence?). Maybe quads learn quicker than single core P4s ?!?

Based on version 5 clients, however I don't think the time stats code was changed for version 6. Threadmaster will cause a different stat to change; cpu effeciency. The end result is the same though.

The DCF is a whole other calculation. It goes up quickly but down slowly and it is easier to estimate how long it will take as a number of tasks. This one reflects how accurately the project has estimated the difficulty of their tasks.


Next 20

Copyright © 2021 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.