24 hour rally - Page 6

gd_barnes · 2008-02-09, 19:11

Quote:

Originally Posted by em99010pepe

First result just came in:

OK, I've been running my Dell 1.66 Ghz duo all night long on LLRnet on 2 cores and am just letting it continue. It's recently complete composites from about n=327990-328000. Can you verify that these have gotten into the rally?

Just got back from picking up kid from driving school...

I'm starting 2 more Athlon cores now, 1 core on a 3.2 Ghz P4 in ~15 mins., and may get 2 cores on my kid's dual-core Athlon within an hour - total 7; 3 fast ones and 4 slower ones.

Gary

gd_barnes · 2008-02-09, 19:17

OK, I've got 5 old k/n pairs from last night to test on both cores of my Athlon DC. Will those get counted in the rally? The exponents will be smaller. One is ~326000; the other ~327000.

Loading software on my 3.2 Ghz P4 now...

Gary

ET_ · 2008-02-09, 19:18

Quote:

Originally Posted by gd_barnes

OK, I've been running my Dell 1.66 Ghz duo all night long on LLRnet on 2 cores and am just letting it continue. It's recently complete composites from about n=327990-328000. Can you verify that these have gotten into the rally?

Just got back from picking up kid from driving school...

I'm starting 2 more Athlon cores now, 1 core on a 3.2 Ghz P4 in ~15 mins., and may get 2 cores on my kid's dual-core Athlon within an hour - total 7; 3 fast ones and 4 slower ones.

Gary

Gary, my P4 3.2GHz seems quite slow, with 1.23sec per iteration.
Prescott family.

Can you confirm?

Luigi

Mini-Geek · 2008-02-09, 19:26

Quote:

Originally Posted by ET_

Gary, my P4 3.2GHz seems quite slow, with 1.23sec per iteration.
Prescott family.

Can you confirm?

Luigi

My 2.5 GHz Athlon (and, I hear, Athlons are slower than Intel for this kind of thing) is getting ~0.6-0.75 ms/iter, so that probably is slower than expected.
BTW I've completed 16 since the rally began. 202 total. (that's my two cores combined, so 8/core since rally, 101/core total)

em99010pepe · 2008-02-09, 19:37

Quote:

Originally Posted by gd_barnes

.... It's recently complete composites from about n=327990-328000. Can you verify that these have gotten into the rally?

Gary

Yep, they are in....

Quote:

Originally Posted by ET_

Gary, my P4 3.2GHz seems quite slow, with 1.23sec per iteration.

That's very slow indeed. I get 0.6 ms/iter on an P4 3.0GHz. Even my slowest machine, an AMD 64 3000+, is faster! Please clean the dust of the fan...

gd_barnes · 2008-02-09, 19:53

OK, I or we have a problem. I haven't been fed any work in about 10 mins. on my two dual-core Athlon's. Theyare 'sleeping' waiting for k/n pairs. My Dell CD and 3.2 GHz P4 seem to be running fine.

What's up here?

I'll try disconnecting and reconnecting the two Athlons. One of them was running fine initially. The other I just started 10 mins. ago and it's been 'sleeping' the whole time.

Gary

em99010pepe · 2008-02-09, 19:57

Try to open port 300 (TCP and UDP) on windows firewall...How are all your machines connected?

gd_barnes · 2008-02-09, 19:58

Quote:

Originally Posted by gd_barnes

OK, I or we have a problem. I haven't been fed any work in about 10 mins. on my two dual-core Athlon's. Theyare 'sleeping' waiting for k/n pairs. My Dell CD and 3.2 GHz P4 seem to be running fine.

What's up here?

I'll try disconnecting and reconnecting the two Athlons. One of them was running fine initially. The other I just started 10 mins. ago and it's been 'sleeping' the whole time.

Gary

Even after the disconnect and reconnect, they are still sleeping. I do not know what this means other than I'm not being fed work. The ports that I have them assigned to are 6993, 6994, 6996, and 6997.

I've changed all occurrences of port 6999 in every file that was in the group of downloaded files.

HELP!! I'm losing time. My Athlon worked fine in test.

Gary

gd_barnes · 2008-02-09, 20:00

Quote:

Originally Posted by em99010pepe

Try to open port 300 (TCP and UDP) on windows firewall...How are all your machines connected?

There are all home machines. There is no firewall. I'm stupid with this stuff. What do you mean by how are they are connected? I wouldn't know anything about 'opening' a port. Can you give detailed instructions?

EDIT: The two Athlon's are running Windows Vista. The Dell CD and P4 are running Windows XP. But still one of the Athlon's worked fine in testing last night so I don't understand this.

ET_ · 2008-02-09, 20:00

Quote:

Originally Posted by gd_barnes

Even after the disconnect and reconnect, they are still sleeping. I do not know what this means other than I'm not being fed work. The ports that I have them assigned to are 6993, 6994, 6996, and 6997.

I've changed all occurrences of port 6999 in every file that was in the group of downloaded files.

HELP!! I'm losing time. My Athlon worked fine in test.

Gary

I set up port 6999 in ALL the machines on my LAN, except for the second core of my Athlon. It works fine.

Luigi

em99010pepe · 2008-02-09, 20:01

Those are the GUI ports, for several cores at the same machine they must be different.

Code:

NPLB_LLRserver current status :
nil
Proposing pair 767/328146 to Free-DC_IronBits
connection closed (socket 372)
connection request from b6ccb9d8:28723 (socket 400)
Proposing pair 843/328146 to XtremeSystems_glennpat
connection closed (socket 400)
connection request from a289684b:53679 (socket 340)
connection request from 92c74451:17020 (socket 380)
Proposing pair 873/328146 to michaf
connection closed (socket 380)
connection request from 829ea741:16612 (socket 276)
Proposing pair 891/328146 to gd_barnes
connection closed (socket 276)
connection request from f13ac948:1436 (socket 268)
Proposing pair 475/328147 to Free-DC_IronBits
Proposing pair 421/328147 to AES
connection closed (socket 268)
connection request from 75242c52:2229 (socket 380)
Proposing pair 489/328147 to Flatlander
connection closed (socket 380)
connection closed (socket 340)
connection request from 22489c1:2435 (socket 372)
Proposing pair 493/328147 to Free-DC_em99010pepe
connection closed (socket 372)
connection request from f13ac948:4002 (socket 400)
Proposing pair 615/328147 to Free-DC_IronBits
connection closed (socket 400)
connection request from b6ccb9d8:28731 (socket 340)
Proposing pair 639/328147 to XtremeSystems_glennpat
connection request from 6bfbf355:2357 (socket 276)
Proposing pair 645/328147 to Free-DC_em99010pepe
connection closed (socket 276)
connection closed (socket 340)
connection request from a289684b:53685 (socket 372)
connection request from 92c74451:17021 (socket 268)
connection closed (socket 268)
connection request from 75242c52:2230 (socket 380)
Proposing pair 871/328147 to Flatlander
connection closed (socket 380)
connection request from f13ac948:1446 (socket 276)
Proposing pair 885/328147 to Free-DC_IronBits
Proposing pair 819/328147 to AES
connection closed (socket 276)
connection request from a289684b:53686 (socket 268)
connection request from 200a8c0:1158 (socket 312)
Proposing pair 979/328147 to em99010pepe
connection closed (socket 312)
connection closed (socket 372)
connection request from f13ac948:4003 (socket 400)
Proposing pair 495/328148 to Free-DC_IronBits
connection closed (socket 400)
connection request from 200a8c0:1159 (socket 340)
Proposing pair 687/328148 to em99010pepe
connection closed (socket 340)
Proposing pair 647/328148 to AES
connection closed (socket 268)
connection request from 200a8c0:1160 (socket 380)
Proposing pair 825/328148 to em99010pepe
connection closed (socket 380)
connection request from f13ac948:4010 (socket 276)
Proposing pair 827/328148 to Free-DC_IronBits
connection request from 22489c1:4971 (socket 372)
Proposing pair 845/328148 to Free-DC_em99010pepe
connection closed (socket 276)
connection request from d5821b18:53210 (socket 268)
Proposing pair 899/328148 to gd_barnes
connection closed (socket 372)
Proposing pair 987/328148 to gd_barnes
connection request from 7bdbc24c:3622 (socket 400)
Proposing pair 525/328149 to gd_barnes
Proposing pair 559/328149 to gd_barnes
Proposing pair 679/328149 to gd_barnes
Proposing pair 615/328149 to XtremeSystems__glennpat
connection closed (socket 268)
connection closed (socket 400)
connection request from d5821b18:53211 (socket 340)
Proposing pair 747/328149 to gd_barnes
connection request from 22489c1:2055 (socket 380)
Proposing pair 769/328149 to Free-DC_em99010pepe
connection closed (socket 380)
Proposing pair 837/328149 to gd_barnes
Proposing pair 867/328149 to gd_barnes
Proposing pair 955/328149 to gd_barnes
Proposing pair 483/328150 to gd_barnes
connection closed (socket 340)
connection request from f13ac948:4014 (socket 372)
Proposing pair 591/328150 to Free-DC_IronBits
connection closed (socket 372)
connection request from 200a8c0:1161 (socket 400)
Proposing pair 593/328150 to em99010pepe
connection closed (socket 400)
connection request from a289684b:1331 (socket 340)
Proposing pair 695/328150 to AES
connection closed (socket 340)
connection request from b6ccb9d8:28754 (socket 372)
Proposing pair 713/328150 to XtremeSystems_glennpat
connection closed (socket 372)
connection request from 20cf8554:4361 (socket 400)
Proposing pair 747/328150 to kar_bon
connection closed (socket 400)
connection request from 6518bb48:2417 (socket 340)
Proposing pair 761/328150 to Free-DC_paratima
connection closed (socket 340)
connection request from a289684b:53688 (socket 372)
connection request from 75242c52:2233 (socket 276)
Proposing pair 783/328150 to Flatlander
connection closed (socket 276)
Proposing pair 917/328150 to AES
connection request from f13ac948:1481 (socket 268)
Proposing pair 923/328150 to Free-DC_IronBits
connection closed (socket 268)
connection closed (socket 372)
connection request from 92c74451:17023 (socket 400)
connection closed (socket 400)
connection request from b6ccb9d8:28759 (socket 340)
Proposing pair 933/328150 to XtremeSystems_glennpat
connection closed (socket 340)
connection request from b6ccb9d8:28760 (socket 372)
connection request from a289684b:53718 (socket 380)
Proposing pair 975/328150 to XtremeSystems_glennpat
connection closed (socket 372)
connection request from 75242c52:2234 (socket 400)
Proposing pair 445/328151 to AES
Proposing pair 459/328151 to Flatlander
connection closed (socket 400)
connection closed (socket 380)
connection request from 8c47b46:2966 (socket 276)
Proposing pair 573/328151 to Mini-Geek
connection closed (socket 276)
connection request from f13ac948:4025 (socket 268)
connection request from 200a8c0:1162 (socket 340)
Proposing pair 579/328151 to em99010pepe
connection closed (socket 340)
Proposing pair 591/328151 to Free-DC_IronBits
connection closed (socket 268)
connection request from 200a8c0:1163 (socket 380)
Proposing pair 661/328151 to em99010pepe
connection closed (socket 380)
connection request from 8c47b46:2967 (socket 276)
Proposing pair 703/328151 to Mini-Geek
connection closed (socket 276)
connection request from 6518bb48:2425 (socket 268)
Proposing pair 745/328151 to Free-DC_paratima
connection closed (socket 268)
connection request from f13ac948:4026 (socket 380)
Proposing pair 789/328151 to Free-DC_IronBits
connection closed (socket 380)
connection request from 829ea741:16812 (socket 276)
Proposing pair 841/328151 to gd_barnes
connection closed (socket 276)
connection request from a289684b:53719 (socket 268)
connection request from a2c0156:52797 (socket 372)
Proposing pair 855/328151 to Free-DC_Petey
connection closed (socket 372)
connection request from 200a8c0:1164 (socket 400)
Proposing pair 865/328151 to em99010pepe
connection closed (socket 400)
connection request from 7bdbc24c:4883 (socket 340)
Proposing pair 885/328151 to XtremeSystems__glennpat
connection closed (socket 340)
connection request from 7fb64d51:4676 (socket 372)
Proposing pair 955/328151 to Free-DC_alpha
connection closed (socket 372)
Proposing pair 913/328151 to AES
connection request from 179bcbd5:63741 (socket 400)
Proposing pair 503/328152 to Team_Italia_ET_
connection closed (socket 400)
connection request from a289684b:53720 (socket 340)
connection request from 829ea741:16816 (socket 336)
Proposing pair 567/328152 to gd_barnes
connection closed (socket 268)
connection closed (socket 336)
connection request from f13ac948:4030 (socket 368)
Proposing pair 585/328152 to Free-DC_IronBits
connection closed (socket 368)
Proposing pair 593/328152 to AES
connection request from 179bcbd5:3226 (socket 312)
Proposing pair 627/328152 to Team_Italia_ET_
connection closed (socket 340)
connection request from 92c74451:17026 (socket 372)
connection closed (socket 312)
Proposing pair 669/328152 to michaf
connection closed (socket 372)

2008-02-09, 19:57	#62
em99010pepe Sep 2004 2·5·283 Posts	Try to open port 300 (TCP and UDP) on windows firewall...How are all your machines connected? Last fiddled with by em99010pepe on 2008-02-09 at 19:57

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
24 hour news	davieddy	Soap Box	4	2011-12-19 19:35
mfaktc slows on WinXP after about an hour	Christenson	GPU Computing	5	2011-05-27 21:47
Prime 95 shuts down itself after exactly 9:22 hour	Unregistered	Information & Answers	13	2009-09-02 05:11
! hour limit on editing	davieddy	Lounge	7	2009-09-01 15:57
1 buck an hour	crash893	Hardware	6	2009-06-18 01:45

2008-02-09, 19:17	#57
gd_barnes May 2007 Kansas; USA 3³·5·7·11 Posts	OK, I've got 5 old k/n pairs from last night to test on both cores of my Athlon DC. Will those get counted in the rally? The exponents will be smaller. One is ~326000; the other ~327000. Loading software on my 3.2 Ghz P4 now... Gary

2008-02-09, 19:53	#61
gd_barnes May 2007 Kansas; USA 289B₁₆ Posts	OK, I or we have a problem. I haven't been fed any work in about 10 mins. on my two dual-core Athlon's. Theyare 'sleeping' waiting for k/n pairs. My Dell CD and 3.2 GHz P4 seem to be running fine. What's up here? I'll try disconnecting and reconnecting the two Athlons. One of them was running fine initially. The other I just started 10 mins. ago and it's been 'sleeping' the whole time. Gary