Problem with logic of the queue

Message boards : Questions and problems : Problem with logic of the queue
Message board moderation

To post messages, you must log in.

AuthorMessage
Erik

Send message
Joined: 3 Apr 09
Posts: 1
United States
Message 24091 - Posted: 3 Apr 2009, 15:31:30 UTC

This problem pertains to CUDA users.

The problem I'm having is that if I set my preferences to allow seti-enchanced & astropulse, two scenarios happen frequently:

1) I get ALL seti-enchanced-CUDA work units. Since my queue is now full, it won't even check for other work units that would put my CPUs to work.

2)I get ALL astropulse or simple-seti work units. Again, now my queue is full, and won't look for CUDA work units that my GPU could use.

I believe that the queue should be seperated for CPU work units and GPU work units. Or am I missing something?
ID: 24091 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15483
Netherlands
Message 24092 - Posted: 3 Apr 2009, 15:34:51 UTC - in response to Message 24091.  

The upcoming BOINC 6.6 client has a separated CPU and GPU scheduler. This will easier fetch work for both than the present 6.4 clients do, as they are hampered by only having one CPU scheduler that's supposed to cater for both.
ID: 24092 · Report as offensive

Message boards : Questions and problems : Problem with logic of the queue

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.