I know about how to limit BOINC settings in the preferences menu, but I would like to restrict my Atom netbook from processing more than one VLAR at a time, as it tends to slow it down too much.

I currently have to suspend one task when I need more CPU available and have 2 VLAR tasks active.

Keith

you could always just adjust your computing preferences on your account page

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

you could always just adjust your computing preferences on your account page

I thought the website preferences http://setiathome.berkeley.edu/prefs.php?subset=global give the same options as BOINC Manager preferences, I notice there are separate sections for [Home], [School] and [Work].

I don't think it answers my problem, what I want to do is ensure that CPU is only allowed to crunch 1 VLAR task at a time as these seem to use more system resources than other tasks.

It is not currently a problem for normal web browsing or audio apps, but when I view video it lags a bit until BOINC decides to suspend processing.

[edit]

Just noticed that I may have looked at the wrong set of preferences online, http://setiathome.berkeley.edu/prefs.php?subset=project is the one for SETI. However after reading a few other threads here, I decided to allow work for SETI Beta again, and I now have a non VLAR task from that project.

[/edit]

they may be VLARs. I'm not all that sure that they actually label their WU's as VLAR

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

I have noticed that when a multicore machine has a VLAR task running on all cores of the CPU it does tend to bog things down a bit. To the point I have snoozed BOINC if I actually needed to do something on the box. This is most noticeable on my dual Xeon with 24 task running.

IIRC it is because VLAR tasks make more use of the memory bus or something along those lines. If that is the case it might be a good idea for the BOINC guys to add something like a "memory load" value that tasks can be flagged with. Then a value could be set in the app which would limit how many of such tasks ran at once. The mechanics would have to be decided on. As the tasks, at least in this project, are being inspected and flagged as VLARs. It may not be that much more for the server to do during task generation.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I have noticed that when a multicore machine has a VLAR task running on all cores of the CPU it does tend to bog things down a bit. To the point I have snoozed BOINC if I actually needed to do something on the box. This is most noticeable on my dual Xeon with 24 task running.

IIRC it is because VLAR tasks make more use of the memory bus or something along those lines. If that is the case it might be a good idea for the BOINC guys to add something like a "memory load" value that tasks can be flagged with. Then a value could be set in the app which would limit how many of such tasks ran at once. The mechanics would have to be decided on. As the tasks, at least in this project, are being inspected and flagged as VLARs. It may not be that much more for the server to do during task generation.

I was going to make a coment then remembered that I only "use" 3 out of 4 cores on this machine, when running all VLAR's on CPU I have not noticed any slowdown.

Yesterday I was running VLAR's on my GPU's, I back off the GPU's from 3 to 1 WU before rescheduling the VLAR's over to GPU's, allthough the GPU's are working lighter than usual, less work and running cooler I do still notice the extra loading that they put on the cards.

The effects on the GPU's are lower than the loading that is now on the cards, having run out of SETI WU's I have been reduced to processing Einstein on GPU's:-(

---

Kevin