LHC@home

http://lhcathome.cern.ch/workunit.php?wuid=973422

Gotta love those P133's taking almost 4 days and 5hrs just to do 1 large WU.

Next time LHC has work it may do one again :D

---

BOINC@Hull . xfire . mySpace

That's pretty funny and it's not even due to the W98 problem that causes the cpu time to increase even when a wu is preempted. It would be better off doing SETI@home and using the optimised SETI application, especially since it gets less granted credit than claimed.

Live long and crunch.

---

Paul
(S@H1 8888)
BOINC/SAH BETA

http://lhcathome.cern.ch/workunit.php?wuid=973422

Gotta love those P133's taking almost 4 days and 5hrs just to do 1 large WU.

Good heavens! You actually have Windows XP on that?! Is it truly installed or part of some kind of cluster?

---

http://lhcathome.cern.ch/workunit.php?wuid=973422

Gotta love those P133's taking almost 4 days and 5hrs just to do 1 large WU.

Good heavens! You actually have Windows XP on that?! Is it truly installed or part of some kind of cluster?

you might get better throughput with win98 or 95 - a typical P133 has rather small memory for the huge needs of XP, and a lot of that proc time os almost certainly swapping operating system in and out whenever the app makes a system call

Just a thought...

---

That's pretty funny and it's not even due to the W98 problem that causes the cpu time to increase even when a wu is preempted. It would be better off doing SETI@home and using the optimised SETI application, especially since it gets less granted credit than claimed.

Live long and crunch.

Every time it tries a SETI WU, after 50hrs it always seems to have a computational error. ATM its either on LHC or SZTAKI :D

---

BOINC@Hull . xfire . mySpace

http://lhcathome.cern.ch/workunit.php?wuid=973422

Gotta love those P133's taking almost 4 days and 5hrs just to do 1 large WU.

Good heavens! You actually have Windows XP on that?! Is it truly installed or part of some kind of cluster?

It is truly installed on a 3.2GB HDD.

you might get better throughput with win98 or 95 - a typical P133 has rather small memory for the huge needs of XP, and a lot of that proc time os almost certainly swapping operating system in and out whenever the app makes a system call

My CPU effieciency on an LHC WU of 95.15% begs to differ =D I think in that machine there is 96MB RAM, and it runs fine as long as I only access it through boincView. Note, XP only requires 64MB.

---

BOINC@Hull . xfire . mySpace

That's pretty funny and it's not even due to the W98 problem that causes the cpu time to increase even when a wu is preempted. It would be better off doing SETI@home and using the optimised SETI application, especially since it gets less granted credit than claimed.

Live long and crunch.

I had a simmilar problem. I thought it was LHC on WinXPSP2 but it was only occuring on one of my XP boxes. So I left it alone.

---

Click here to join the #1 Aussie Alliance on LHC.

http://lhcathome.cern.ch/workunit.php?wuid=973422

Gotta love those P133's taking almost 4 days and 5hrs just to do 1 large WU.

Next time LHC has work it may do one again :D

If I had enoughf memory in my P133 I would run it, but only 16 megs. The cost of additional memory would be better spent on a faster CPU for one of the other systems.

Got a free IBM Aptiva with an AMD K6 cpu, seems to run good. Have more PC100 memory for that, will have to put it in and try BOINC on it. Don't know the speed of that K6, will have to run CPUz on it to find out. If nothing else I can get a cheap board and a celeron cpu for a 3rd cruncher, no would be better off getting a HT CPU for this one. Anyone have an used early P4 HT, 2.4 or 2.6 gig (socket 478) to sell cheap? But then this board is probably to early to support HT.

Ray

---

Pizza@Home - Rays Place - Rays place Forums

My wife had a 486SX25 notebook, have not run BOINC on that eather as it only has 4 megs of memory. But from the speed of that you can figure that it would take at least 5 times longer than a P133. Than you figure in that the 486SX processors had no floteing point unit and for this dubble the time.

---

Pizza@Home - Rays Place - Rays place Forums

I had a simmilar problem. I thought it was LHC on WinXPSP2 but it was only occuring on one of my XP boxes. So I left it alone.

No, I was wrong. It is LHC and it's happening on my only Win98SE box

---

Click here to join the #1 Aussie Alliance on LHC.

http://lhcathome.cern.ch/workunit.php?wuid=973422

Gotta love those P133's taking almost 4 days and 5hrs just to do 1 large WU.

Next time LHC has work it may do one again :D

It could be 40% worse -
http://lhcathome.cern.ch/show_host_detail.php?hostid=43358
took ~509 000 s for one of the last lot - which turned out to be 6 days, 23 and a bit hours. Still met the seven-day deadline though!

Is the P133 really a straight Pentium (i586) chip? BOINC claimed LHC had no clients for the i586-pc-linux-gnu platform, but that may be a Windows vs Linux thing. I ask as I've got a spare P233 chip (neener-neener-neener! :) ) but I'm not sure I can be bothered to upgrade the thing as I can't decide whether the abysmal performance is down to a cheap Cyrix FPU or the memory banned-width of the 72-pin SIMMs...
And I think I'm getting rid of it soon - but then I said that a couple of years ago too!

Thanks

Henry

Is the P133 really a straight Pentium (i586) chip?

http://www.boincathull.co.uk/p133.png

Does that answer your question? :p

borandi

---

BOINC@Hull . xfire . mySpace

Is the P133 really a straight Pentium (i586) chip?

That is it, one of the early Pentium chips. Only diferance between that and the earlier P60 & P90 chips is the speed.

But when they came out they were really considered fast, the fastest 486 (486DX4 100) was slow compaired the the Pentiums.

I can remember that the first Pentium chips were really expensive for the first couple of Mounths, and most people thought that only larger companies that needed a lot of computing power would evev use the pentium chip. But as you can see years later they were wrong.

I have never seen a 286, 386 or 486 chip crunching except for one 486 working on SETI but it is taking close to a week per WU there. Definately not good for projects with shorter deadlines.

Ray

---

Pizza@Home - Rays Place - Rays place Forums

I can remember that the first Pentium chips were really expensive for the first couple of Mounths, and most people thought that only larger companies that needed a lot of computing power would evev use the pentium chip. But as you can see years later they were wrong.

That is not quite as bad as IBM's howler, determining that there would only ever be a market for about sis computers, at a time when English Electric had already got orders for that number in the UK alone... the very first being sold to a tea company

Sometimes we all can be a bit slow when it comes to seeing what use will be made of new crunch power.

Or the power of the marketing department...

R~~

I have never seen a 286, 386 or 486 chip crunching except for one 486 working on SETI but it is taking close to a week per WU there. Definately not good for projects with shorter deadlines.

My 486 (AMD 586-133) does SETI in 12.5 days. It's not really worth it. SIMAP seems to be a good choice for slower computers. The 486 does it in 22 hours and I'm almost always first to return a result.

My 486 (AMD 586-133) does SETI in 12.5 days. It's not really worth it. SIMAP seems to be a good choice for slower computers. The 486 does it in 22 hours and I'm almost always first to return a result.

SZTAKI is also a good one for slower computers. I put it on all my 400Mhz and below.

---

BOINC@Hull . xfire . mySpace