Custom Query (981 matches)
Results (7 - 9 of 981)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #832 | fixed | Screen saver on 2 monitors | ||
| Description |
I am running BOINC on several computers and found this problem only on the one that has 2 monitors. Sometimes (I know, not much help here) when the screen saver is ON and I move the mouse to turn it off, the first monitor keeps the image of the screen saver frozen. I do not have the problem if I press ESC instead of moving the mouse. Since I password protect my screen my only solution is to go to another PC and restart my PC remotely The PC with the problem is a Dell GX620, windows XP SP3 and 2 19" Dell flat panel |
|||
| #325 | wontfix | Force project applications to single core (Windows) | ||
| Description |
BOINC preferences allow users to set a maximum number of cores to use at one time... however under windows a thread is distributed between all the cores (but is still limited to %50 of of the processing power). For example, on my Quad-core machine I run three threads... but instead of three cores being at 100 percent and 1 being at 10 or so (for whatever other system tasks may be running) all four cores are at 75% or so. This is very inefficient because not only are you increasing the amount of cache used (because you're populating all four caches with the information of all three projects as opposed to one different project on three of the four cores). But it will also slow down the work-unit because of timing (one core must wait for the others to finish). While project mangers COULD release their applications with flags limiting each thread to one processor/core they don't... however Windows lets this option be set on a per instance basis (in the task manger), or every time the executable is started using imagecfg.exe (available in tool-kits, or google it). Seeing as imagecfg works on a command-line basis it might even be possible to use it as-is. |
|||
| #414 | invalid | BOINC client should prioritize next work packet based on return time | ||
| Description |
This is just a suggestion- Seeing how my computer uses the BOINC client, I think it would be most beneficial to prioritize the next started task by the return deadline, not the order received. seeing my computer I could see where a slower computer would possibly miss deadlines by working on tasks that were not due before ones that have a closer deadline. |
|||
