A Benchmark just in case you're wondering

Message boards : Number crunching : A Benchmark just in case you're wondering
Message board moderation

To post messages, you must log in.

AuthorMessage
nemesis
Avatar

Send message
Joined: 12 Oct 99
Posts: 1408
Credit: 35,074,350
RAC: 0
Message 131474 - Posted: 2 Jul 2005, 4:08:22 UTC

56 hours 47 minutes
for a K6-2+ 550mhz.

it was painful to watch.
ID: 131474 · Report as offensive
N/A
Volunteer tester

Send message
Joined: 18 May 01
Posts: 3718
Credit: 93,649
RAC: 0
Message 131488 - Posted: 2 Jul 2005, 4:51:58 UTC - in response to Message 131474.  

[font='courier,courier new']Are you referring to this host?[/font]
ID: 131488 · Report as offensive
nemesis
Avatar

Send message
Joined: 12 Oct 99
Posts: 1408
Credit: 35,074,350
RAC: 0
Message 131491 - Posted: 2 Jul 2005, 5:01:27 UTC

yes
ID: 131491 · Report as offensive
N/A
Volunteer tester

Send message
Joined: 18 May 01
Posts: 3718
Credit: 93,649
RAC: 0
Message 131512 - Posted: 2 Jul 2005, 5:54:54 UTC - in response to Message 131491.  

[font='courier,courier new']That WU had better be ET's "Hello, Earthlings" message - 56 hours is far too long...

And if it isn't, I feel your pain.[/font]
ID: 131512 · Report as offensive
nemesis
Avatar

Send message
Joined: 12 Oct 99
Posts: 1408
Credit: 35,074,350
RAC: 0
Message 131517 - Posted: 2 Jul 2005, 6:09:50 UTC

yeah i think that is the last unit it will crunch..
gonna flip it over to linux and do some work ...
that isn't so ummm difficult.

amazing how the AMD chips got soooo much better...lol


ID: 131517 · Report as offensive
Profile John Cropper
Avatar

Send message
Joined: 3 May 00
Posts: 444
Credit: 416,933
RAC: 0
United States
Message 131598 - Posted: 2 Jul 2005, 12:38:12 UTC - in response to Message 131474.  

56 hours 47 minutes
for a K6-2+ 550mhz. it was painful to watch.


My old 133MHz used to average between 85 and 110 hours per WU. I got ten good years out of it and eventually replaced it with an AMD 1.8 (~3.5 hours/WU) a couple months ago.


Stewie: So, is there any tread left on the tires? Or at this point would it be like throwing a hot dog down a hallway?

Fox Sunday (US) at 9PM ET/PT
ID: 131598 · Report as offensive
Alinator
Volunteer tester

Send message
Joined: 19 Apr 05
Posts: 4178
Credit: 4,647,982
RAC: 0
United States
Message 131610 - Posted: 2 Jul 2005, 13:33:09 UTC - in response to Message 131474.  

56 hours 47 minutes
for a K6-2+ 550mhz.

it was painful to watch.


You short on RAM in it? I have three K6-2/500's and they do a lot better than that. The slowest of the three only has 92 MB and still runs a result in about 31 hours, and the faster ones (192 and 256 MB) in about 24 hours.

In fact I have a K6/300 with 192 MB and it runs one in 39.5 hours.

Alinator
ID: 131610 · Report as offensive
ampoliros
Volunteer tester
Avatar

Send message
Joined: 24 Sep 99
Posts: 152
Credit: 3,542,579
RAC: 5
United States
Message 131630 - Posted: 2 Jul 2005, 14:50:41 UTC

I had a K6 running at 473MHz that only took 20 to 22 hours to complete a WU.

When the optimized clients for windows started coming out, I replaced the stock client on it and it actually took longer (28 hours). It was then that I decided to put that pc out to pasture.

7,049 S@H Classic Credits
ID: 131630 · Report as offensive
nemesis
Avatar

Send message
Joined: 12 Oct 99
Posts: 1408
Credit: 35,074,350
RAC: 0
Message 132065 - Posted: 3 Jul 2005, 14:47:39 UTC

it has 192mb of pc100 ram...
seti-boinc was the only program running other than the usual
windows me background foundation.

no big loss, it has now been assimilated
into the linux farm doing other things...


ID: 132065 · Report as offensive
Profile 3quarks

Send message
Joined: 19 Jun 03
Posts: 95
Credit: 354,773
RAC: 0
United Kingdom
Message 132073 - Posted: 3 Jul 2005, 15:33:15 UTC - in response to Message 132065.  

it has 192mb of pc100 ram...
seti-boinc was the only program running other than the usual
windows me background foundation.

[snip]



Sounds way too slow, I had an K6 400 that dropped down to running at something like 64hrs a unit, when I retired it, found that the CPU fan had stopped spinning (due to melting), so that may have been the problem, don't know for sure as it hasn't crunched since.
ID: 132073 · Report as offensive

Message boards : Number crunching : A Benchmark just in case you're wondering


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.