![]() |
If mine sieves close to yours, I'm happy to give it another 24-36hr on the GPU to perhaps find improvement. But when my first effort scored 10% worse than yours, I admit to losing interest.
-Curtis |
I'll have a try at Schickel's 572000:3135 150 digit number. Mainly to test my scripts for poly searching, but I'll post the best one I find.
Chris |
[QUOTE=chris2be8;365532]I'll have a try at Schickel's 572000:3135 150 digit number. Mainly to test my scripts for poly searching, but I'll post the best one I find.
Chris[/QUOTE]OK, thanks for the run; I'll start a job when you post a poly. |
Don't wait. It looks as if the PSU could not take the extra load. It won't even turn the fans any more. I'll have to take the PC to a repair shop tomorrow for a new PSU (if that's what failed).
I've already had to buy a better CPU cooler to replace the stock one. Adding the cost of a new PSU to that and it'll about double the cost of the GPU. Chris |
[QUOTE=chris2be8;365553]Don't wait. It looks as if the PSU could not take the extra load. It won't even turn the fans any more. I'll have to take the PC to a repair shop tomorrow for a new PSU (if that's what failed).
I've already had to buy a better CPU cooler to replace the stock one. Adding the cost of a new PSU to that and it'll about double the cost of the GPU. Chris[/QUOTE]Sorry to hear that. I'll go ahead and run a test today then to see which of the 3 polys sieves faster. |
[QUOTE=VBCurtis;365457]If mine sieves close to yours, I'm happy to give it another 24-36hr on the GPU to perhaps find improvement. But when my first effort scored 10% worse than yours, I admit to losing interest.
-Curtis[/QUOTE]My next jobs are going to be larger, so I assume they will benefit more from an intensive GPU search. As it stands, my highest poly and your poly sieved about the same speed, with yours faster by a hair, but the yield for yours was ~13% less..... I should have my answer in ~10 days or so. |
OK, thanks for the info. I'll proceed to RichD's C160 once I finish a job for my own composite; I should have a first poly Thursday evening, and will let it run until Sunday. A C160 should have 10+ GPU days of poly search, but I don't have the resources available to do that.
|
for the C184, I reverted back to quintic, and got
[code] R0: -189739683797999317529400126331832722 R1: 693895955161095043 A0: 32453832495498028059546140602061149196755545 A1: 1293761121414808264524462998111743706 A2: -228832774841744122536924096105 A3: -20926589075998572306546 A4: -345246593021584 A5: 35193264 skew 19710555.98, size 3.593e-018, alpha -6.391, combined = 3.765e-014 rroots = 3 [/code] |
For the C160 from 3408:1385, the first day's search turned up a score 1.19e-12. The window msieve "expects" is 1.33e-12 to 1.52e-12.
I will post any poly that improves on this 1.19 score. -Curtis |
For what it's worth I've run -npr against the best 100 (of 2669441) entries in msieve.dat.ms from my run on Tuesday. I got: [code]
R0: -135858192791394956439864945410 R1: 570849297736093 A0: 14301565586950358401384714963946613561 A1: 16152650324808439814192471692756 A2: 3567237672198900849530610 A3: -879298234954072455 A4: -49781921806 A5: 3864 skew 7818935.60, size 2.043e-14, alpha -7.261, combined = 6.747e-12 rroots = 3 elapsed time 00:09:43 [/code] That's probably not very good since the GPU didn't run for very long before the PSU died. Elapsed time above is for npr only. Chris |
For the C160 from 3408:1385
[code]expecting poly E from 1.33e-012 to > 1.52e-012 R0 -4033130224608614852170208876887 R1 180460901903302283 A0 -52357711339572497186925087177217184640 A1 428629807184883242734908451572136 A2 -111194134081525777552853666 A3 -93001930969062599969 A4 9212558892474 A5 3828720 skew 3102530.12, size 1.335e-015, alpha -7.118, combined = 1.333e-012 rroots = 5[/code] I have no polys above 1.19 except this one. I'll give it one more day to improve, but this is a usable candidate in my opinion. |
| All times are UTC. The time now is 22:51. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.