mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   PrimeNet (https://www.mersenneforum.org/forumdisplay.php?f=11)
-   -   OFFICIAL "SERVER PROBLEMS" THREAD (https://www.mersenneforum.org/showthread.php?t=5758)

kladner 2015-04-28 06:31

[QUOTE]
Here's one for someone to run with and see what happens:
[URL="http://www.mersenne.org/M23562031"]M23562031[/URL]
[/QUOTE]
I started to run it from 60-67, but even with two cores' affinity it was painfully slow. I restarted from 64, and it outran MISFIT's automatic stats update. No factors where I ran.

James Heinrich 2015-04-28 14:22

[QUOTE=Madpoo;401079]Here's one for someone to run with and see what happens: [URL="http://www.mersenne.org/M23562031"]M23562031[/URL][/QUOTE][code][Tue Apr 28 10:20:23 2015]
UID: JamesHeinrich/mfaktc_GTX580, no factor for M23562031 from 2^1 to 2^70 [mfaktc 0.21 75bit_mul32_gs][/code]

petrw1 2015-04-28 15:31

[QUOTE=James Heinrich;401100][code][Tue Apr 28 10:20:23 2015]
UID: JamesHeinrich/mfaktc_GTX580, no factor for M23562031 from 2^1 to 2^70 [mfaktc 0.21 75bit_mul32_gs][/code][/QUOTE]

I was of the understanding that mfaktc does not work under 64 bits?
Or there is a special port but it works slowly?

Am I confused?

James Heinrich 2015-04-28 15:53

[QUOTE=petrw1;401105]I was of the understanding that mfaktc does not work under 64 bits? Or there is a special port but it works slowly? Am I confused?[/QUOTE]You are confused :smile:
v0.20 did not support:
* exponents below M1,000,000
* GPU sieving below 2[sup]64[/sup]

v0.21 dropped the exponent limit from M1,000,000 to M100,000
v0.21 also extended GPU sieving below 2[sup]64[/sup]. It's faster than CPU sieving, but (significantly) slower than GPU sieving above 2[sup]64[/sup].

kladner 2015-04-28 18:38

[QUOTE=James Heinrich;401109]You are confused :smile:
v0.20 did not support:
* exponents below M1,000,000
* GPU sieving below 2[sup]64[/sup]

v0.21 dropped the exponent limit from M1,000,000 to M100,000
v0.21 also extended GPU sieving below 2[sup]64[/sup]. It's faster than CPU sieving, but (significantly) slower than GPU sieving above 2[sup]64[/sup].[/QUOTE]

Eek! I just realized that in my last round of experimentation I left v0.20 in residence. Time to fix that!

Madpoo 2015-04-28 22:23

[QUOTE=kladner;401086]I started to run it from 60-67, but even with two cores' affinity it was painfully slow. I restarted from 64, and it outran MISFIT's automatic stats update. No factors where I ran.[/QUOTE]

I picked one of my dev boxes with 12 cores and I'm having it do TF work on 583 exponents where only sannerud has done anything (at least in v5).

I don't have a fancy schmancy GPU so I'm only taking these up to 2^62.

Once that's done, is there anyone or ones interested in looking at this list for rechecking from 2^62 up to whatever? In almost all of them, sannerud reported them up to 2^67, 2^68 or 2^69 which is more than I'd want to bite off without a GPU or seven available. :smile: But at least you'll know they're at least done to 2^62 reliably.

Mark Rose 2015-04-28 22:33

[QUOTE=Madpoo;401158]I picked one of my dev boxes with 12 cores and I'm having it do TF work on 583 exponents where only sannerud has done anything (at least in v5).

I don't have a fancy schmancy GPU so I'm only taking these up to 2^62.

Once that's done, is there anyone or ones interested in looking at this list for rechecking from 2^62 up to whatever? In almost all of them, sannerud reported them up to 2^67, 2^68 or 2^69 which is more than I'd want to bite off without a GPU or seven available. :smile: But at least you'll know they're at least done to 2^62 reliably.[/QUOTE]

Is this a new list separate from the list in the other thread?

Madpoo 2015-04-28 22:38

[QUOTE=Mark Rose;401160]Is this a new list separate from the list in the other thread?[/QUOTE]

I don't know... I'd have to cross check. Maybe I can get to that tonight.

Mark Rose 2015-04-28 23:27

[QUOTE=Madpoo;401161]I don't know... I'd have to cross check. Maybe I can get to that tonight.[/QUOTE]

It could save you significant work. Another reason for saving duplicate TF work in the database.

Madpoo 2015-04-29 01:34

[QUOTE=Mark Rose;401172]It could save you significant work. Another reason for saving duplicate TF work in the database.[/QUOTE]

I just checked against that list. No repeats.

These new ones I'm looking at go from 23.2M to 49.9M, which is about where that other list George created starts out.

By the way, be sure to give George and James a wave and an "attaboy" for working on getting these v4 logs together. I don't know what format they were in originally but James wrangled them into a format that matched the v5 results and we got them added in to the database.

We're not totally done checking it all out for data issues but so far it all seems like it's in good shape.

Madpoo 2015-04-29 01:53

1 Attachment(s)
[QUOTE=Madpoo;401183]I just checked against that list. No repeats.

These new ones I'm looking at go from 23.2M to 49.9M, which is about where that other list George created starts out.
[/QUOTE]

Attached is a list I generated of those exponents. I created worktodo.txt compatible entries for them with a starting point of 62-bits since that's what I got them all retested up to. I just put in 69 bits as the "to bits" since that's the furthest sannerud took any of them (some were 67, some 68).

Since these are exponents where I didn't see anyone do any other work at all, it doesn't really matter how far sannerud took them to... nobody took 'em any further.

There will still be some exponents to look at after these. Some of them will be where sannerud did checking of part of the range but someone else took it further. Those are a little more complex to sort out so I'll get to those later. This list ought to be a good start though for anyone interested.


All times are UTC. The time now is 23:12.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.