C216_121_113 done
 

[code]
Tue Jan 10 03:52:25 2017 p90 factor: 580921215695212868302417364096458795652940323405161943166066741346510662807047003583315151
Tue Jan 10 03:52:25 2017 p126 factor: 316900545134900491040409938835673641976865489322415780272967951839090786438785279124799187800716970860432073102237853864604547
[/code]

75.6 hours on 7 threads E5-2650v2 for 12.45M density-112 matrix (128 was too much).

Log attached and at [url]http://pastebin.com/5azCd6m5[/url]

I'll take C230_132_73 next.
(I'll wait for < 1M pending to start. It will probably need every bit.)

C186_145_72
 

[QUOTE=YuL;450118]post-processing of C186_145_72, can I have it please?[/QUOTE]

LA is in progress, expect the factors in another 8 days.

P55 (20156...)^5-1 (14e)
 

In 14e, reserving P55 (20156...)^5-1 next.

C192_124_97 Factored
 

[code]
prp75 factor: 139709832089514662716934860196942078349011590443455720471980872603618418559
prp117 factor: 875393327935842936941980169983745848311995991208520724560123589147999362485173744957503892747393159821303128819147523
[/code]

Reserving 9468940004449^17 - 1 for post processing.

Reserving 10^249+45*10^124-1.

C230_132_73 factored
 

After a restart guessing 56 hours to solve a 8.6M matrix, -t 4, TD=132.
[CODE]p85 factor: 8391265267215246404028349491059337114898870838203592884248856059483529015250340360787
p145 factor: 1485102219016607854454861141423520459412898312694617650460323043388810810393303224280165442696524918199965610875495060392704660499488544081415547[/CODE]

13*2^789-1 factored
 

[code]prp61 factor: 1311890846639943631674593733057633656292355142160708183898109
prp156 factor: 734318244531928186132824716241631517606935103045878610316941913043124282438235124674431034790876287625366814660791012533897262982703683332985323193499396281[/code]
8.45M matrix at TD=128. ~80 hrs on 6 threads of a 5820 running 6 threads of ECM also.
360M raw relations at 32LP yielded 298M unique. Matrix did not build at TD 136.

[QUOTE=VBCurtis;451008][code]prp61 factor: 1311890846639943631674593733057633656292355142160708183898109
prp156 factor: 734318244531928186132824716241631517606935103045878610316941913043124282438235124674431034790876287625366814660791012533897262982703683332985323193499396281[/code]
8.45M matrix at TD=128. ~80 hrs on 6 threads of a 5820 running 6 threads of ECM also.
360M raw relations at 32LP yielded 298M unique. Matrix did not build at TD 136.[/QUOTE]

Can you copy the log to pastebin.com and post it here? Thanks.

The log for 13*2^789-1 is attached. I went to pastebin, and don't see how to create anything without making an account.

[QUOTE=VBCurtis;451023]The log for 13*2^789-1 is attached. I went to pastebin, and don't see how to create anything without making an account.[/QUOTE]

Okay, I've done it and updated the status page.

For future reference, there's no need for an account. Just go to pastebin.com and paste text of your choice into the box labeled "New Paste". Bonus points if you also fill in the "Paste Name / Title:" field with something useful. Then hit the "Create New Paste" button. That's it. The resulting page will have a URL you can pass around.

Reserving 147^47+47^147 if it is available.

Running 842592:8053, this is quite a big matrix and will take about two weeks.

145^72+72^145 cofactor (15e)
 

[URL="http://www.factordb.com/index.php?id=1000000000044691169"]145^72+72^145[/URL] is factored
[CODE]Fri Jan 20 14:55:09 2017 p86 factor: 87703786972364019431608195397058749092287547928991667456672843153075868703107613442793
Fri Jan 20 14:55:09 2017 p100 factor: 2210021286715014614290405621775603377151959634601407815051621353068190619444766329420677291802010633
[/CODE]

LA on a 18.9e6 matrix took ~9.2 days using 2x 6 threads on dual Xeon E5-2620 @2.0GHz (target_density=132).
Log attached and at [URL]http://pastebin.com/km9t4KkG[/URL]

[QUOTE=YuL;451289]
LA on a 18.9e6 matrix took ~9.2 days using 2x 6 threads on dual Xeon E5-2620 @2.0GHz (target_density=132).[/QUOTE]

YuL-
When you say "2x6 threads", do you mean you used MPI to keep one set of 6 processes distinct from the other set, to keep the data local to each CPU? I ask because I have a dual-Xeon 5650 (6 cores each, 12 total) on the way, and plan on tackling some big matrices with it. Can I just invoke msieve -t 12 {etc}, or should I be mucking about with MPI and/or taskset to split the job?
I suppose "can" isn't quite what I mean; can someone quantify the speedup from a more advanced use than "msieve -t 12 {etc}"?

[QUOTE=VBCurtis;451292]YuL-
When you say "2x6 threads", do you mean you used MPI to keep one set of 6 processes distinct from the other set, to keep the data local to each CPU? I ask because I have a dual-Xeon 5650 (6 cores each, 12 total) on the way, and plan on tackling some big matrices with it. Can I just invoke msieve -t 12 {etc}, or should I be mucking about with MPI and/or taskset to split the job?
I suppose "can" isn't quite what I mean; can someone quantify the speedup from a more advanced use than "msieve -t 12 {etc}"?[/QUOTE]

Here is what I do: I run two processes in a 2x1 MPI grid by running
[CODE]mpiexec -np 2 --map-by socket --bind-to socket %mpi_msieve% -v -t 6 ...
[/CODE]
one process runs on CPU1 the other runs on CPU2, it is faster than running
just one msieve -t 6 or msieve -t 12 but unfortunately I can't give you the
numbers right now.

That's exactly what I was looking for, thank you!

[QUOTE=VBCurtis;451331]That's exactly what I was looking for, thank you![/QUOTE]

You're welcome, here are some numbers:

- Using 2x 6 threads (with MPI as explained in previous post):

[CODE]Wed Jan 11 09:14:20 2017 linear algebra at 0.0%, ETA 234h15m
Wed Jan 11 09:14:43 2017 checkpointing every 90000 dimensions
Fri Jan 20 13:12:01 2017 lanczos halted after 298905 iterations (dim = 18901676)
Fri Jan 20 13:12:27 2017 recovered 35 nontrivial dependencies
Fri Jan 20 13:12:29 2017 BLanczosTime: 795869
Fri Jan 20 13:12:29 2017 elapsed time 221:04:31
[/CODE]

- Using only one process with -t 6:
[CODE]Sat Jan 21 17:58:15 2017 commencing Lanczos iteration (6 threads)
Sat Jan 21 17:58:15 2017 memory use: 8046.8 MB
Sat Jan 21 18:00:09 2017 linear algebra at 0.0%, ETA 376h14m
[/CODE]

- Using only one process with -t 12:
[CODE]Sat Jan 21 18:06:00 2017 commencing Lanczos iteration (12 threads)
Sat Jan 21 18:06:00 2017 memory use: 8047.0 MB
Sat Jan 21 18:07:29 2017 linear algebra at 0.0%, ETA 293h23m
[/CODE]

I'll take P55 (19269...)^5-1 next.

P55_20156_5_m1
 

[URL="http://www.factordb.com/index.php?id=1100000000685458984"]P55(20156...)^5-1[/URL] is factored.
[CODE]Tue Jan 24 05:58:26 2017 p84 factor: 940322013842066118893478552199628075999679084425590323928948290553565322827151582101
Tue Jan 24 05:58:26 2017 p121 factor: 1537670403026780958260264404077531779849152647548875287040060122513827450125721017592918041375946498047702440132660850381
[/CODE]

LA on a 6.23e6 matrix took ~27.7 hours using 6 threads on Core i7-5820K (target_density=136).
Log attached and at [URL]http://pastebin.com/3YLXMB1X[/URL].

10^249+45*10^124-1 completed - 102 hours for 10.5M matrix (TD=130)

[CODE]prp97 factor: 1058314134576003349770157576757398261341275637591655186457355903095338293154242250572586542471071
prp149 factor: 47570811597419943430756398431048875252430079438673794780755089544997090197565725745187114326495767160629829316527724400223086541540148348903597430663
[/CODE]

[url]http://pastebin.com/3quHtP2E[/url]

C196_145_47 (14e)
 

Taking C196_145_47 next.

19218301^31 - 1
 

Reserving 19218301^31 - 1 if it is available.

P55 (19269...)^5-1 factored
 

Guessing about 24 hours to solve a 6.1M matrix, -t 4, TD=130. (TD-136 failed)
The machine wasn't idle at the beginning of LA.
[CODE]p94 factor: 3925488933189879342183094944089294977855388227825677716724995836344555324592472843330479439711
p116 factor: 27965361357645581827621384004007663549053808145883995338373731940837851218015431830810603685286723811342793252094611[/CODE]

P55 (19269...)^5-1 Log
 

Got it to work - I think.

[url]http://pastebin.com/mdS0wmbw[/url]

13*2^905-1 produced filtering message "matrix not dense enough, retrying" a few times, finally building a matrix of density 40 (target density was set to 140). After ~70 hrs of LA, only the trivial dependencies were recovered.

Restarting postprocessing with filter_maxrels set to 310M.

Next time, is "matrix not dense enough, retrying" the sort of nearly-fatal message that should incite me to restart filtering with fewer relations?

[QUOTE=VBCurtis;451645]Next time, is "matrix not dense enough, retrying" the sort of nearly-fatal message that should incite me to restart filtering with fewer relations?[/QUOTE]

I saw that message once but didn't think much about it because it eventually completed. But it was a 10 day solve.

[url]http://pastebin.com/SvXfm9Wh[/url]

[QUOTE=VBCurtis;451645]13*2^905-1 produced filtering message "matrix not dense enough, retrying" a few times, finally building a matrix of density 40 (target density was set to 140). After ~70 hrs of LA, only the trivial dependencies were recovered.

Restarting postprocessing with filter_maxrels set to 310M.

Next time, is "matrix not dense enough, retrying" the sort of nearly-fatal message that should incite me to restart filtering with fewer relations?[/QUOTE]

Strangely enough, that message seems to appear in two different situations. One is that there aren't enough relations, and the other is that there are too many. In practice I've only seen it in the latter situation.

In this case, the number was way oversieved. For a 31-bit job, 250M should have been plenty. Some extra can produce a smaller matrix, but 350M is firmly in the territory where one sees this problem. I would probably have just started with maxrels set to 300M.

9+5_295 (15e)
 

Reserving 9+5_295 from the 15e queue.

I'll take 32668561^31-1 next.

[QUOTE=swellman;451501]Reserving 19218301^31 - 1 if it is available.[/QUOTE]


[code]
prp76 factor: 2758005348426399256471975117475109030251493697251061390611599493168874121569
prp103 factor: 7812280223399775417889125540463887990280512149934969036205872019610582450050573879946788206077444320093
[/code]

C222_125_92
 

Reserving C222_125_92.

13*2^905-1 factors
 

[code]prp62 factor: 46205165266133662482948385141378840157279684813622824070309817
prp110 factor: 29742352095538657419873460130787243208882192833790233431382969850597187601711543963363200375101906633497733877[/code]

Log attached. [url]http://pastebin.com/y7CjDbUa[/url]

C186 from 842592:8053 done
 

[code]
p61 factor: 2828552482149628110952085410657566731619129765282892686071101
p126 factor: 129999454062486614642509451137992207528880979362609412660254837839413317446553082608089399055348960433331952479568500186490943
[/code]

22.26M matrix at density 120 took around 255 hours on 7 threads E5-2650v2.

Log attached and at [url]http://pastebin.com/mjjhwWvC[/url]

[QUOTE=swellman;450942]Reserving 9468940004449^17 - 1 for post processing.[/QUOTE]

[code]
prp71 factor: 49319570324911942576065847490549577181702305054656307368513056057736237
prp117 factor: 236408236208426095318413372774730508091627951849214226624392009594648988074456868955277552955382718640478169517494601
[/code]

32668561^31 - 1 factored
 

44 hours to solve 8.1M matrix, -t 4, TD=132.
[CODE]p90 factor: 967658557768716749610734895304160851507055761110076840945687873209014376821441224950181973
p91 factor: 2016177673321603188279887659453574552093217578530020613538746544181185422441560665538029389[/CODE]

[url]http://pastebin.com/LYticT07[/url]

C253_131_91
 

[code]
prp63 factor: 412580299763086788439432891134232544893325616058658679884438447
prp190 factor: 6149259025664753795047382263078659630867118432854248477434894244711511737307523105698154597144083332495835939760326170191284059674802325791734554732145526069977315581448337047191802208983141
[/code]

Reserving C213_121_106 for postprocessing.

Reserving C197_148_45 for postprocessing.

I'll take 63601^47 - 1 next.

[QUOTE=swellman;451070]Reserving 147^47+47^147 if it is available.[/QUOTE]

[code]
prp64 factor: 1695384298021839502232996427930932218038983338495135414567052323
prp181 factor: 5010548153512043281070364557509701397159932771889452298611218118829105045228894625247934836029847086221012408231427834910558157156020665394811394339689390310451934037121846665559163
[/code]

Reserving 208097431^29 - 1 for postprocessing.

Reserving 11040:i10009 (14e).

11040:i10009 (14e) factored
 

[code]
p72 factor: 775898870020476216696184664461654051399795643550104257138082780543548133
p88 factor: 5683127607046441994171561569150576380641472996757704762493444625879644146850783691062169
[/code]

Log: [url]http://pastebin.com/ssDUBw4t[/url]

You're fast! :smile:

[QUOTE=unconnected;452617]You're fast! :smile:[/QUOTE]

Yeah, turns out it was only a five-minute job! :wink:

[COLOR="White"]Or maybe I forgot to reserve it until I had already finished.[/COLOR]

C196_145_47 (14e)
 

[URL="http://www.factordb.com/index.php?id=1000000000044666169"]C196_145_47[/URL] is factored.
[CODE]Thu Feb 9 19:49:23 2017 p95 factor: 70388691093282095318679209704350138885179063229374774658874821536066589715263195779872587630737
Thu Feb 9 19:49:23 2017 p101 factor: 21873385553971467291232075200553210680862429106922640517847471222240196880808216411231043016463915349
[/CODE]

Linear algebra on a 11.25e6 matrix took ~99.5h on Core i7-5820K using 6 threads (td=136).
Log attached and at [URL]http://pastebin.com/vHssKTdS[/URL]

I'll take P40 (15461...)^7-1 next.

63601^47 - 1 factored
 

24 hours to solve a 6.1M matrix, -t 4, TD=132.
[CODE]p68 factor: 98154676299810150162428700461631550211260266910725768110772852570707
p122 factor: 12275931600799268425990058740366172290601311960099425503455205629347731794911347693015920409804513925041446458284029635131[/CODE][URL]http://pastebin.com/xRVKYtVS[/URL]

[QUOTE=swellman;451795]Reserving C222_125_92.[/QUOTE]

[code]
prp68 factor: 21299989689308079923315948084168105637864846529748332056330566741609
prp154 factor: 7026898539456056966557841584974057705339129997988682473615973306848631574021784126898631721788062104020673985520609895133244319566953398819580310223693363
[/code]

I'll take P39 (83661...)^7-1 next.

P40 (15461...)^7-1 factored
 

25 hours to solve a 6.1M matrix, -t 4, TD=132.
[CODE]p65 factor: 10005625842923582651161921912411177900788037436690433181132811923
p122 factor: 16469442787564412242916425259141280339835292057450620679836631736778345903093559115176544022359791884081180567351147672043[/CODE][URL]http://pastebin.com/0pdmmzxj[/URL]

I'll take P40 (12838...)^7-1 next.

I'll take 4018159^37 - 1.

P39 (83661...)^7-1 factored
 

22 hours to solve 5.8M matrix, -t 4, TD=132
[CODE]p65 factor: 73072064895604753819464653814519444176588339127522722989549203661
p114 factor: 775417187818720729774723141286083280338900403275815120822848196839330965264468310633922687956964348980758776714949[/CODE][URL]http://pastebin.com/6DkqWNE1[/URL]

[QUOTE=swellman;451741]Reserving 9+5_295 from the 15e queue.[/QUOTE]

[code]
prp87 factor: 933900028622213862262887338396817775002590554391106487265886662743767841426102074263521
prp95 factor: 48867618106091989558299265209498912839035211304918084783433487321999640399101885500594310904661
[/code]

[QUOTE=VBCurtis;452432]Reserving C197_148_45 for postprocessing.[/QUOTE]

[code]prp92 factor: 22417311950349298809261913533527577138565312266987678898226045304117205663811252476551951241
prp105 factor: 683841813906927308587057344016275400840324353873501189112607210362787406497575348465879097034158003192197[/code]

[url]http://pastebin.com/H4Ct3yCD[/url]

P40 (12838...)^7-1 factored
 

24 hours to solve a 6.0M matrix, -t 4, TD=132. (TD=136 failed)
[CODE]p61 factor: 1505729338682566727787436639324536805353483841674955788761521
p121 factor: 1476591019727920407653683517394062359921794475378095885349024526794105158569830000369777884710556679192301524490273368667[/CODE][URL]http://pastebin.com/Nnk8sZue[/URL]

I'll take 1727870509^23 - 1 next (when it finishes up).

Reseving 842592:i8057.

1727870509^23 - 1 factored
 

12.5 hours to solve a 4.6M matrix, -t 4, TD=132.
[CODE]p95 factor: 60209350309812814601217514916112316975686098415049363162394913916883435280223075594925125075877
p101 factor: 25860128498887018518543318563713509743589255102278180240735490671778284981038880587023448752737785733[/CODE]
[url]http://pastebin.com/g6PANq7h[/url]

I'll take 5968930061879^17 - 1 next.

C162_842592_8057 completed - 25 hours on 5.7M matrix (TD=120)

[CODE]prp57 factor: 104304086290455323809128634102435227766937882115656117107
prp106 factor: 8325151841003029467861119602284441808058362833319881303330188753777822203935604346486242684549679946970483
[/CODE][URL]http://pastebin.com/SzNGpRHc[/URL]

13,792- factored:
[code]prp85 factor: 4673326347390629492295131952262103974354737317495818184487075033103632380532494446813
prp104 factor: 14240563615698695173704628574678048686371976762910968250671276878866416959434282440114943020931522151437[/code]

363M raw relations yielded 308M unique relations, and a matrix of 9.2M at density 125 (130 failed to build).
Someone added q=120M to 140M to the grid after I downloaded the relations file, so I didn't use those additional relations; 360M raw relations is sufficient for 32LP jobs at this size (at least, with these small poly coefficients).

[url]http://pastebin.com/79Yi2vZq[/url]

[QUOTE=swellman;452264]Reserving C213_121_106 for postprocessing.[/QUOTE]

[code]
prp100 factor: 7033884415243028663831688947990396907006107575102640138748511602068587240578626616628981733134626953
prp113 factor: 34433822247463457420968600056067169730444536753951179218756243105548375098067860790955375180820397602224666576367
elapsed time 330:09:07, TD=120
[/code]

Reserving 126^113+113^126 from 15e.

[QUOTE=VBCurtis;453425]13,792- factored:
[/QUOTE]

Forgive me for being rude, but I understand 13,792- to mean 13^792-1, as does FactorDB. However these factors do not divide 13^792-1. Can you explain what you mean here, please?

2^792*13-1

[QUOTE=BudgieJane;453821]Forgive me for being rude, but I understand 13,792- to mean 13^792-1, as does FactorDB. However these factors do not divide 13^792-1. Can you explain what you mean here, please?[/QUOTE]

Sorry! On mklasson's site (the person who tracks these factors), that is the notation used. The intended number is 13*2^792-1. By this time, I should know better.

[QUOTE=VBCurtis;453826]Sorry! On mklasson's site (the person who tracks these factors), that is the notation used. The intended number is 13*2^792-1. By this time, I should know better.[/QUOTE]

Thank you.

Taking C196_5889307277311_17m1_c

ETA morning of Monday 6 March

I'll take 137^62+62^137 next.

Reserving[SIZE=2] C170_11040_10011.[/SIZE]

Approximately how much memory would be needed to post-process C171_829332_3638 with 250M relations?

[QUOTE=richs;454121]Approximately how much memory would be needed to post-process C171_829332_3638 with 250M relations?[/QUOTE]

It will fit very happily in 12 or 16GB, it might be a bit of a squeeze in 8GB but would probably work if you're not doing anything else on the machine.

[QUOTE=fivemack;454122]It will fit very happily in 12 or 16GB, it might be a bit of a squeeze in 8GB but would probably work if you're not doing anything else on the machine.[/QUOTE]

Thanks! I have 8GB on my i7 so I could give it a try if folks don't mind possibly giving me a little coaching.

[QUOTE=richs;454126]Thanks! I have 8GB on my i7 so I could give it a try if folks don't mind possibly giving me a little coaching.[/QUOTE]

I'm pretty sure it'll fit in 8GB, and I'll try to answer any questions you have. I'll also be happy to run it in case it proves too big for your machine.

That's a 32-bit job. Won't it need more that 250M relations? Maybe not 470M but in the mid 300s at least?

I've done 32-bit jobs from the 14e queue with a similar setup to you and they worked out ok. Might take a lot of time to complete LA but it is satisfying.

I estimated the number of relations from the number of initial work units, so it will be higher.

And thanks for the offer of help, Mike!

I did 13*2^792-1 last week, an easy (poly score 4.966e-13) 14e/32 job. 363M raw relations used 6024MB in filtering to produce a 9.2M matrix @ density 125, which needed 4450MB during LA phase (numbers are according to msieve log, not actual linux measurements).

I think filtering can use less memory if need be, so I wager you'll be under 7GB with a 400M-raw-relation dataset and resulting matrix.

I would like to reserve C171_829332_3638 for post-processing. I will need access to the relations once sieving completes. Thanks!

[QUOTE=swellman;453313]I'll take 5968930061879^17 - 1 next.[/QUOTE]


[code]
p65 factor: 67849296658910202638236872898732152289040015765930562806894158817
p133 factor: 9557001891513408855310148609047847559610677485509231368807615979293548031074739739951016065008718445835591297587278389614337023202913
[/code]

(pastebin YwGwnKW7)

5889307277311^17-1 done
 

[code]
Sun Mar 5 10:02:47 2017 p86 factor: 21588019131624480261213087632709663292583462891151385038718915822758374406951788530943
Sun Mar 5 10:02:47 2017 p111 factor: 176646497198850457553292214249179221490224586309155662390586032473559390190002961108376410217304210195190394473
[/code]

About 98 hours for 14.4M density-130 matrix on 7 threads E5/2650v2.

Log attached and at [url]http://pastebin.com/ZPfvZB5C[/url]

[QUOTE=swellman;452562]Reserving 208097431^29 - 1 for postprocessing.[/QUOTE]

[code]
prp72 factor: 479742431059899110994219659235419426436829832082725748378461202046141921
prp157 factor: 8350328379652436747351674454307900719812060578861929059570435118933396153109546842482294937852663973122824597736959360610336689355237898364862406790728934631
[/code]

C170_11040_10011 completed - 78 hours for 8.8M matrix (TD=130).

[CODE]prp74 factor: 14047136646188050446426835099176188962663379379189902708325392410675208339
prp97 factor: 1150083075710523146375060759448680577494243136308133454856648773912418908208898808662687249189679[/CODE][URL]http://pastebin.com/wHymMBFL[/URL]

[QUOTE=swellman;453810]Reserving 126^113+113^126 from 15e.[/QUOTE]

[code]
p95 factor: 10578261744514909560599836322653261103599860208813690229435687421017146215229232340080627789417
p96 factor: 285536096317424768098176289887064232541622413161158482230251586704610125035739172384253801083629
[/code]

C272_141_86 finally done
 

[code]
Sat Jan 7 10:29:17 2017 matrix is 44075825 x 44076073 (16741.0 MB) with weight 4225609544 (95.87/col)
Sat Jan 7 10:29:17 2017 sparse part has weight 3947789421 (89.57/col)
...
Sun Mar 12 23:08:27 2017 BLanczosTime: 5579086
Sun Mar 12 23:08:27 2017 elapsed time 1549:44:47
...
Mon Mar 13 14:01:37 2017 p87 factor: 447836130646209608046040122882238481249684585332009693026080705032115342619260496121499
Mon Mar 13 14:01:37 2017 p110 factor: 42834814977725477464082637412272306370552506826726901458563977926692491010849716750807265440614257179277647039
[/code]

1549 hours on six threads i7/5820K for a 44.08M matrix (density 160). Log attached and at [url]http://pastebin.com/cBRyViLy[/url]

I'll take C204_19xx41_11 next from the 14e queue.

I'll take C172_327668647153_19 once sieving is complete.

I'll take C201_142_80 (ETA morning of 20 March)

[QUOTE=swellman;452852]I'll take 4018159^37 - 1.[/QUOTE]


[code]
prp57 factor: 135548320583621340036652989436372477851397776060447819133
prp182 factor: 41009286458906896128598529848605933893628728984062220190440804182817893733878020853362745214767127739326133846210453493997523089317038309268718590414487668576523647467915034385125237
[/code]

Reserving Aliquot sequence 829332 step 3638.

Rich Smith

I'll take C237_12119_59 next.

Question on 143^93+93^143
 

I recently upgraded my best machine to 32Gb - can it handle 143^93+93^143 (a 33-bit job)? My fear is being able to filter/digest the relations but LA taking months on an i7-3610QM processor. It's a fun machine but it is still a laptop.

Any advice?

[QUOTE=swellman;455005]I recently upgraded my best machine to 32Gb - can it handle 143^93+93^143 (a 33-bit job)? My fear is being able to filter/digest the relations but LA taking months on an i7-3610QM processor. It's a fun machine but it is still a laptop.

Any advice?[/QUOTE]

The last 33-bit job I did took nine weeks on a 32GB i7/5820K, which has two more cores and a significantly better memory subsystem, and is in a water-cooled desktop machine that ran unattended 24/7. It used more than 20GB of memory for the nine weeks.

I think probably you'd be biting off more than you can chew.

[QUOTE=fivemack;455020]The last 33-bit job I did took nine weeks on a 32GB i7/5820K, which has two more cores and a significantly better memory subsystem, and is in a water-cooled desktop machine that ran unattended 24/7. It used more than 20GB of memory for the nine weeks.

I think probably you'd be biting off more than you can chew.[/QUOTE]

Another dream dashed on the rocks of reality! Thank you for the sage advice - I will not take on that particular monster.