Heh. More like "Turn your head and cough".
PowerShell is, in fact, rather powerful. But it focuses on system administration rather than general purpose programming.

Success for 1.69[CODE]Processing result: M( 26275721 )C, 0x8c6e4dc676cb816a, n = 1474560, CUDALucas v1.69
LL test successfully completes double-check of M26275721
[/CODE]

OT
 

[QUOTE=chalsall;293795]Indeed...

If I may be a little "catty" here, it constantly blows my mind that the most popular Operating System in the world doesn't let the Power User do the most basic of things at the Command Line.[/QUOTE]The MPOSITW didn't become the most popular by catering to Power Users (or by keeping track of all its memory allocations).

Wow, look what I have started :smile:

In the midst of it I hardly even noticed 1.69 success report.

But to stay off topic: PowerShell is extremely powerful but it is not portable and requires a bit of different thinking. I looked into it but since I already have cygwin I was too lazy to get used to it. Anyway i did write couple of scrips that were easier to implement with it than with perl and cygwin.

Andriy

I'd like to put together a CUAlucas performance comparison chart, similar to what I have for [url=http://mersenne-aries.sili.net/mfaktc.php]mfaktc[/url]. I'll need a wider variety of data samples than the single one I have from my own system. If anyone reading this thread could fire up CUDAlucas and PM/email me some iteration times for a variety of exponent sizes (at least 25M, 50M and 75M would be great). If possible, a variety of CUDAlucas versions would also be interesting. Naturally I'd also need to know what GPU you're using (and at what clock speed, if overclocked (whether factory or by yourself)).

[QUOTE=James Heinrich;293952]I'd like to put together a CUAlucas performance comparison chart, similar to what I have for [URL="http://mersenne-aries.sili.net/mfaktc.php"]mfaktc[/URL]. I'll need a wider variety of data samples than the single one I have from my own system. If anyone reading this thread could fire up CUDAlucas and PM/email me some iteration times for a variety of exponent sizes (at least 25M, 50M and 75M would be great). If possible, a variety of CUDAlucas versions would also be interesting. Naturally I'd also need to know what GPU you're using (and at what clock speed, if overclocked (whether factory or by yourself)).[/QUOTE]


I'll compile some data for you. It may take me a few days to get it all.

On a bad note, I had a 1.69 mismatch today. I'm re-running the exponent to see if the original is bad, but it will need a P95 run anyway. Anyone want to run it? If not, I'll start P95 on it Saturday when my other P95 DC completes.

M( 26229943 )C, 0x2bb14485101dd1__, n = 1474560, CUDALucas v1.69

How long would your run take?

[QUOTE=Dubslow;293958]How long would your run take?[/QUOTE]

My CuLu DC will be done in 14 hours. Since it's a DC for me I'll run it on a slower laptop;the P95 run will take about a week. Can you run it faster?

Yeah, I think I can do it in a few days. I'll run it now.

[QUOTE=Dubslow;293962]Yeah, I think I can do it in a few days. I'll run it now.[/QUOTE]
Cool, thanks :smile:. I'll post my CuLu re-run results when it's done...

Edit: I attatched the full run test (minus the last residue)

Wait, whoops...
When you reported the result, you lost the assignment key and it was reassigned. I'd rather not poach...

Edit: Repeat for emphasis: If you want me to do a quick DC with Prime95, you must not submit the result to PrimeNet, so that we retain control of the exponent. (Yes, that does mean checking the residue for a match before submitting.) Sorry about that flash.