Boinc multiple gpu11/30/2023 (which has been there starting with the 6.6.36 client and appears to have gotten significantly worse with the 6.10.x series). That this draws seemingly little or no comment suggests something of a case of 'dropping the ball' regarding design considerations or attitude. The project/user preference is available to the client, and why the client ignores it strikes me as, shall we say, a 'suboptimal' design choice. I still find it curious that the current iteration of the BOINC client insists on fetching GPU work from projects that don't support GPU work, and then insists on fetching CPU work from projects that don't support CPU work. I just wish the work fetch routine wasn't skewered in the process. That is supports CUDA 2.3 is good as well. That the 6.10.x client supports ATI GPU is an EXCELLENT thing. The only time I need to employ this work around is when I am running Collatz in a workstation project mix.Įventually, I would sincerely hope that the work fetch routines utilize configuration information available to the client and not stress the projects with needless I/O pings nor frustrate users trying to keep a balance of multiproject GPU and CPU tasks on hand. If you are running a mix with GPU and CPU tasks, but NOT running Collatz or an ATI GPU supporting project, then the 6.4.5 client seems the best choice. The ONLY reason at the moment for using the later client is to work with those projects which support ATI GPU (pretty much compels the 6.10.x client) or CUDA 2.3 support (again, I think that requires the 6.10.x client).Īt the moment, if you are running only CPU tasks and not running Vista/Win7 on the Windows side (say Windows XP or 2000), then the 5.4.5 client is the last 'good' one. This procedure works in 32 bit XP, and I suspect 32 bit Vista (haven't tried it there yet). Install the new client over the existing client (though an uninstall Won't work for Collatz since they require the 6.10.x client)ĥ) After developing an overlarge queue for those projects being starvedīy the 6.6.36 and more recent work fetch routine, you can typically POEM and Spinhenge on the CPU side and GPUGrid on the GPU side, it One work around for the current state of the 6.6.36 and more recent client fetch routine:ģ) Reinstall the better fetch handling client 6.4.5Ĥ) Load up on the queues for those projects which are being starvedīy the current fetch design (I find this particularly useful for If you don't want any gpu work, there's an option among the preferences to say so.Īs for not getting any cpu work, it may be that BOINC has decided that your computer has all of the work that it can handle at present.Īnd constantly detaching may be interfering with this. Provided that you stop detaching all of the time, which forces BOINC to re-start it's learning. If you have a graphics card that is suitable for gpu work, and the drivers that are needed for gpu work, then BOINC is programmed to ask each of your projects for gpu work, so that in the event that one of those projects suddenly releases a gpu application, your computer will get some.Īpparently, after a while BOINC will learn not to ask. I have heard tales about I/O constraints with various projects (including SETI), and would think that even if the user level frustration had no bearing in the client design, generating additional useless project I/O hits might motivate the developers to fix this bug (which has been there starting with the 6.6.36 client and appears to have gotten significantly worse with the 6.10.x series). It seems to me that rather than ping the client servers repeatedly for work the project can not send out, the more 'user friendly' and 'project friendly' approach would be to read the configured preferences and USE them. Unfortunately, the functionality which allows the client to figure out resource share from that project configured setting has not been completed to obtain the project specific settings regarding GPU/CPU handling and instead imposes it's own 'logic' regarding GPU or CPU work fetch. I also run some projects which have both CPU and GPU support and have configured them at the project level for GPU only or CPU only. I run multiple CPU only and multiple GPU only projects. I find it curious and frustrating in mixed mode scenarios.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |