![]() |
[QUOTE=swellman;443313][code]
prp72 factor: 978565968924483425382263961480233408815037814502051456105779764121914183 prp109 factor: 2929842661984090798217929968282138600153392406190996246161028706583008524360649211184929775234325778886028099 [/code][/QUOTE] [SIZE=2] [/SIZE][B][SIZE=2]135^109+109^135[/SIZE][/B] [url]http://pastebin.com/qJCZ3C0R[/url] |
Reserving C229_123_88 (14e).
|
C226_137_55 (14e) factored
1 Attachment(s)
C226_137_55 (14e) factored
[CODE] Sun Sep 25 17:32:23 2016 prp63 factor: 165354796458345914605165139424482992513332726208359487846383977 Sun Sep 25 17:32:23 2016 prp164 factor: 28375739241182213806145712923564050394266902673515697209488423961051903418812580320357686672456691080107405632391671848967580919735009082963332078928674035206236369 [/CODE] [url]http://pastebin.com/EX10Vnee[/url] |
C227_124_85 (14e) factored.
[code]
p60 factor: 108800212826185001374072706568640952716258373676667659183611 p168 factor: 268393154893542681183106817555725677151729799204719680086858184705601906445700826230614132065660947457716923168152947284183185289581945455744297230014704572871699264497 [/code] Log: [url]http://pastebin.com/vMSFx8Q5[/url] |
Reserving C239_150_41.
|
Reserving C201_125_82 (14e).
|
C275_150_116 done
1 Attachment(s)
[code]
Mon Sep 26 06:01:54 2016 p78 factor: 122139714038731020536111602858614657766864371087731914277412046815193700189713 Mon Sep 26 06:01:54 2016 p198 factor: 459580917850105287889065963726778800602609609542195130258147374296364925814360418843819514368120005206867026715293706940462991970029221739198362427369877895867613884626968300460272814965030462114657 [/code] About 291 hours on 7 cores E5-2650v2 for 23.6M density-130 matrix. Log attached and at [url]http://pastebin.com/iaj9ZpNS[/url] |
C272_136_105 update
It takes 34 hours to filter the billion relations once (reading from RAID0 hard discs, it might be a bit faster from NVMe SSD). At density 128 I get a 43.64M matrix and a report of 22.3GB memory use at the start of the clique-removal phase. Currently filtering at density 160; binary search at a day and a half per test is tedious but not impractical.
I have done larger matrices in the past ("1539 hours on six cores i7/4930K for the 48.3M^2 matrix") and I now have an i7/5820K, so this is tractable; should definitely be done by Christmas, probably won't be done by American-Thanksgiving. |
[QUOTE=fivemack;443502]It takes 34 hours to filter the billion relations once (reading from RAID0 hard discs, it might be a bit faster from NVMe SSD). At density 128 I get a 43.64M matrix and a report of 22.3GB memory use at the start of the clique-removal phase. Currently filtering at density 160; binary search at a day and a half per test is tedious but not impractical.
I have done larger matrices in the past ("1539 hours on six cores i7/4930K for the 48.3M^2 matrix") and I now have an i7/5820K, so this is tractable; should definitely be done by Christmas, probably won't be done by American-Thanksgiving.[/QUOTE] Thought you would run it on the quad Opteron. |
I might well run on quad-Opteron; but I am not quite sure how fast the quad-Opteron is, and wanted to give a confident upper limit for how long it will take.
|
Reserving C247_125_102 (14e).
|
| All times are UTC. The time now is 23:15. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.