2801^79-1 reservations (CLOSED 27 AUGUST)

[chris2be8]

I didnt get very far:
[chris@localhost o2801_79]$ ../../src/gnfs-lasieve4I15e -r o2801_79.poly -o out28-28.1M -f 28000000 -c 100000
Error: the polynomials don't have a common root:

c0: -1
c1: 0
c2: 0
c3: 0
c4: 0
c5: 0
c6: 2801
Y0: 653236457112135142391905382282254342883556401
Y1: -1

I can't see any errors in the poly:
[chris@localhost o2801_79]$ cat o2801_79.poly

n: 77728012992649681652257138568390176857212890117660654903605188181803793527234365966882492843633887478337495016140443699327828796305552459390410906211419468091843928832883028959106125700776135225351872298944331308559262827186539091839208835236997045999057406305939986879
skew: 0.266
c6: 2801
c0: -1
Y1: -1
Y0: 653236457112135142391905382282254342883556401
lpbr: 32
lpba: 32
mfbr: 64
mfba: 64
alambda: 2.6
rlambda: 2.6
alim: 134217727
rlim: 134217727

Any ideas?

Chris K

[Batalov]

you need a newer binary, e.g. from Jeff's site.
(the binary you have is fairly old - it appears to have the 255-digit limit which was removed something like a year ago)

[Batalov]

My comp will probably (fingers crossed) be relatively free after tomorrow night, so I'll take a crack at my usual 2% (or is it 'my two cents'?).
I'll take the 67-70M and 134-137M regions (will test the schedule arrays and SCHED_TOL, yada-yada-yada).

[apocalypse]

I've had trouble uploading my latest file, and now I can't reach fivemack.dyndns.org at all. Is something wrong, or am I just unlucky?

$ ftp fivemack.dyndns.org
ftp: connect: No route to host

$ ping fivemack.dyndns.org
PING fivemack.dyndns.org (86.173.95.174) 56(84) bytes of data.
^C
--- fivemack.dyndns.org ping statistics ---
36 packets transmitted, 0 received, 100% packet loss, time 35280ms

[fivemack]

I don't know whether it's my ADSL-to-wifi box, my wifi-to-ethernet bridge or my ethernet switch, but sometimes my network connection falls over until I've rebooted some selection of those devices in some order.

[Batalov]

I got lucky. The transfer was stale for a few minutes and then finished fine (Tom fixed the connection probably, right then).

LatSieveTimes: 0.497Ms like a clock for each of the 67M+1M intervals (times 3), then 0.544Ms for 134M+1M (and less yield, but that's all natural) on PhenomII 940 at 3.25GHz. There were no BAD_SCHEDs or yield dips /pats himself on the back/. Going on for another ~1.1 Megasecs.

[Batalov]

Done with 134-137M. Will upload the last MQ-chunk when possible.
The last timings and counts were:
134-135M : 0.54Ms : 1738288 unique, 1699 duplicates (removed)
135-136M : 0.54Ms : 1727485 unique, 1709 duplicates (removed)
136-137M : 0.54Ms : 1730639 unique, 1683 duplicates (removed)

Ran mock filtering on 6MQ-data; there were ~60K intra-range duplicates and 215 wasted relations with 32-bit+ b values (very few, not a problem).

[fivemack]

The new box forwards packets from adsl to wifi very much more reliably than the old box, does not take two-minute thumb-twiddling breaks every ten minutes, does not cause "YOUR WIFI CONNECTION IS COMPROMISED" messages to appear on my Mac Mini whenever it twiddles its thumbs, and has a nice clear configuration interface.

However, the settings configured in the nice clear packet-forwarding configuration interface don't seem to have any effect on the actual forwarding of actual packets. So fivemack.dyndns.org is down until I get this sorted out, sorry.

[mdettweiler]

Originally Posted by fivemack

The new box forwards packets from adsl to wifi very much more reliably than the old box, does not take two-minute thumb-twiddling breaks every ten minutes, does not cause "YOUR WIFI CONNECTION IS COMPROMISED" messages to appear on my Mac Mini whenever it twiddles its thumbs, and has a nice clear configuration interface.

However, the settings configured in the nice clear packet-forwarding configuration interface don't seem to have any effect on the actual forwarding of actual packets. So fivemack.dyndns.org is down until I get this sorted out, sorry.

As a suggestion for the meantime, you guys might want to try uploading relations to http://www.sendspace.com/ -- they use that over at the Aliquot project rather extensively for their team sieves now, and it seems to be reliable and decently fast. And I believe files are stored for at least 30 days (and that's reset every time somebody downloads the file).

Granted, it does have the singular disadvantage that fivemack will have to download the results again after they're uploaded (as opposed to having them uploaded directly to him in one fell swoop), but it might still be useful in helping to clear through some of this upload-pending backlog that's built up.

[smh]

Originally Posted by Andi47

In Windows (64 bit, but 32 bit sievers as they are a bit faster in windows) that's ~414 MB per thread.

Consider running a 64 bit linux virtual machine. The 64 bit linux lasieve is quite a bit faster then the 32 bit windows version.

[Andi47]

Originally Posted by Andi47

Have you got my relations?

BTW: There are lots of reservations which haven't made it into the first posting yet.

Adding my relations to the relation counts given in the 1st posting should give a total relation count of 95,411,621.

How many relations are needed? (sieving from 20-320M should give less than 392M raw relations (95.4M/(93-20)*(320-20) = ~392.1M) ) fivemack: your calculation is wrong because not all the 20-93 range has yet been reported ... I'm expecting 500+M raw relations from the 300MQ.