hey IsOs - how many WUs is your P4 doing a day?

[TuffGuy]

i remember something about you running TWO instances as the same time to saturate the cpu. how's that working for you?

 

[IsOs]

I don't have a P4, just dual PIIIs and dual Athlons.

The PIIIs are no match to the dual Athlons. Dual Athlon Thunderbirds 1.4 GHz on Tiger MP is about 9 per day. The XPs are much faster🙂

 

[TuffGuy]

oopsies... 😱 i realized that after i posted it. but here's barbary's results: (for his dual 2.2ghz p4)

using the ars benchmark unit:
2 Seti Cli no Hyper Threading
Elapsed time 3:42, Results 2, Time per Unit Per CPU 3:42

4 Seit Cli no Hyper Threading
Elapsed time 7:22, Results 4, Time per Unit Per CPU 3:41

4 Seti Cli with Hyper Threading
Elapsed time 5:47, Results 4, Time per Unit Per CPU 2:54

making some assumptions: an individual CPU would be slightly faster than the dually setup, but there should be a similar (positive) effect when running two instances of SETI on it. right?

 

[Def]

Well, those are on dual Xeons that have Hyperthreading enabled. It allows the OS to see each physical processor as two logical ones. In practice, this keeps the execution units better fed with data.

I'm pretty sure enabling two processes on a normal single CPU system will not give any gain. If it is, it will be on the matter of a percent or two faster and IMO it's not worth it due to the extra RAM that the second client takes up.

Defster

 

[TuffGuy]

dang. and i was getting all excited.

 

[BadThad]

To satisfy your curiousity, my P4 system is finally running. It's a 1.8a@2358 MHz (1.650v) with 512MB Corsair 2-2-2 DDR. I have no "hyper-threading" option so I'm just running one instance of SETI using SETI Driver under Win2kPro. My times are running from 2:50 to 3:50 with an average of around 3:20 so far. I've only crunched about 8 wu's, so I will have a more definiative average in a few more days...plus I keep playing with the bus speed and ram timings so nothing is consistent yet.

I'm waiting for Asus to release a new BIOS that will actually let me monitor my cpu core temp. A bug in the P4B266 bios always shows the freaking core temp at 40°C...blaaaa. I have booted to windows at 2400 but I backed off until I can check the core temp because this was at 1.70v. I don't want to fry this cpu quite yet, LOL.