BOINC mgr. wont update project resource preferences for this project only. Any suggestions?

---

I've seen the same issue. I've been told it is an system issue with BOINC itself and not MW. Your preferences will update the next time you get work - stupid really, but that is the wisdom of the BOINC devs.

Just updated.

---

Just updated.

Possibly it won't update boinc untill you receive more wu's. My stats in boinc do that for this project.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Abaucus for sure. Old p4.

---

Abaucus for sure. Old p4.

That's the only one I'm using, a P4 2.66.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Abaucus for sure. Old p4.

That's the only one I'm using, a P4 2.66.

I've got a P4 3.06 too. It gets pretty good RAC for an "old" machine, even though its only 6 months old.
;-p

---

I've got a P4 3.06 too. It gets pretty good RAC for an "old" machine, even though its only 6 months old.
;-p

If you would enable Hyperthreading, the RAC could be even a bit higher ;)
HT gives a nice boost with MW (and some other projects too).

How do I enable Hyperthreading? I would like to improve the RAC if I could. Any tips would be appreciated.

---

You need to activate HT from the BIOS.

As regards preferences ... have you set them on BOINC Manager on the local machine?

---

Go away, I was asleep

I dont see anything about hyperthreading in Boinc manager preferences?

---

Not all P4s had hyperthreading, if there isn't anything in the BIOS about HT, your's doesn't do it.

And in the BOINC preferences, it would just need ot have the number of processors set at 2.

---

Calm Chaos Forum...Join Calm Chaos Now

I dont see anything about hyperthreading in Boinc manager preferences?

Neither have I.

HT is a local machine function. Your P4 may or may not have HT, but if it does it needs that function activated in the BIOS.

I have a dual Xeon with HT on each CPU. The HT is activated in the BIOS, but BOINC and the servers just see a P4 Prestonia quad.

---

Go away, I was asleep

I only have one processor, should I still tell boinc I have 2?I think I'll leave the hyperthreading to someone thats a little more comfortable playing in the Bios than I am.
;-p

---

If it is a HT capable CPU then yes, it will help.

---

4870 GPU
4870 GPU

I think I'll leave the hyperthreading to someone thats a little more comfortable playing in the Bios than I am. ;-p

If you have a compatible CPU it is just one switch there. Nothing to worry about.

Judging from the data of your CPU (Family 15 Model 4 stepping 9) you have a 90nm Prescott in the G1 stepping. Clocked at 3.06GHz it could be either a P4 519K (which got HT disabled) or a P4 524, which is the identical CPU but with enabled HT.
So if you have the latter, a short visit in the BIOS could be beneficial. And not just for BOINC, Windows itself will also behave a bit smoother in quite some cases.

Thanks for the info CP, I'll give it a go in the morning. I'll see what my computers(2) can really do.I checked myP4(used cpu-z) its 519K, oh well. I'll check my Pentium D in the morning.
;-p

---

All you should have to do for the Pentium D is set your prefrences to use 100% of your processors on multiprocessor computers. It should then crunch 2 work units at a time. If it is already doing that then you don't need to change anything.
NI!

---

4870 GPU
4870 GPU

Thanx guys, my pentium D is already running 2 at a time so I guess not much more to do.
;-P

---

I've seen the same issue. I've been told it is an system issue with BOINC itself and not MW. Your preferences will update the next time you get work - stupid really, but that is the wisdom of the BOINC devs.

This was covered in a previous thread.

It is not a BOINC issue, it's an MW specific one.

The default BOINC scheduler behaviour is to issue a host record DB query every time a host initiates a contact session. The reason is precisely so the host can update it's local stat and global preference records.

However, in MW's case the scheduler has been modified so that if there is no work available in the scheduler's local queue, no DB query is issued. The host record query is only issued if the host actually gets a work assignment or it has work to report, because you absolutely have to in that situation.

You can test this right now over at SAH for yourself, since they seem to be having trouble getting work out the door at the moment (the scheduler is reporting no work available).

Tweak a global pref for one of your hosts, then do manual update. You will see the change is passed back to the host immediately, even though there is no work to send.

Alinator