[quote=IronBits;129124]Well, floundering around, I managed to download both links and put them into one directory on the 64bit quad.
I see something about a sr2work.txt file (which I don't have)
and a command line of (and I put it in startup.bat)
sr2sieve -p 10e9 -P 20e9 -i nplb-doublecheck-sieve_10G.txt but I don't have that .txt in that directory.
Now what?

03/13/2008 01:10 AM 8,995,261 sr2data.txt
02/29/2008 10:14 PM 71,680 sr2sieve.exe
03/18/2008 07:03 PM 60 startup.bat[/quote]
sr2data.txt and sr2work.txt are default file names so you don't have to specify via command line. You can create an sr2work.txt and put, e.g. what I'm doing 320-340 and simply run sr2sieve.exe with no command line arguments, and it will test 320G-340G on the inputs in sr2work.txt (sr2work.txt is only in 1G increments so you need command line for smaller increments). If you'd like to use a .bat (which with this if in 1G/e9 increments you don't) you can just say "sr2sieve" without command arguments and it will run.

To sum up: All you need is sr2data.txt, as downloaded, sr2sieve.exe, as downloaded, and sr2work.txt, as you create based on the range assigned. You then run only sr2sieve.exe and it will begin, make a factors file, do checkpoints, etc. etc. on its own.
[quote=IronBits;129126]310G-550G is available
Let me have 549-550 and see how that goes.
How do I put it in the directory and make it work?[/quote]
[quote][COLOR=Red][B]*This range was partially done in a hodgepodge manner by jasong, please post here if you'd like to help fill some gaps in this range.[/B][/COLOR][/quote]You need to post how large of a range you'd like (for reference, a 20G range will take my 2.5 GHz Athlon about 3 days) and Anon will tell you your range(s) from the gaps jasong left.

[quote=gd_barnes;129129]One option, Anon, is for you and I to complete the odd-ball parts of the various ranges so that only ranges that are even multiples of 1 billion are left. That might be the easiest thing for everyone unless you have a lot of reservations in the partially completed ranges that would make it more difficult to start that at this late juncture.[/quote]
Exactly what I was thinking. :smile: I've been filling in small portions of the gaps, as you suggested, so that only multiples of 1 billion (1G) are left. Thus, the ranges can be crunched normally (i.e. with sr2work.txt) rather than needing to have the exact p value specified on the command line. :smile:

[quote=Mini-Geek;129131]sr2data.txt and sr2work.txt are default file names so you don't have to specify via command line. You can create an sr2work.txt and put, e.g. what I'm doing 320-340 and simply run sr2sieve.exe with no command line arguments, and it will test 320G-340G on the inputs in sr2work.txt (sr2work.txt is only in 1G increments so you need command line for smaller increments). If you'd like to use a .bat (which with this if in 1G/e9 increments you don't) you can just say "sr2sieve" without command arguments and it will run.

To sum up: All you need is sr2data.txt, as downloaded, sr2sieve.exe, as downloaded, and sr2work.txt, as you create based on the range assigned. You then run only sr2sieve.exe and it will begin, make a factors file, do checkpoints, etc. etc. on its own.

You need to post how large of a range you'd like (for reference, a 20G range will take my 2.5 GHz Athlon about 3 days) and Anon will tell you your range(s) from the gaps jasong left.[/quote]
Yes, Mini-Geek is correct. You don't need to specify any command line switches, since sr2sieve can grab the range from sr2work.txt.

IronBits, I've picked the range [b]318G-320G[/b] for you. It's a 2G range, which is pretty small, and should be good for the purposes of judging speed. Here's what you need to do to run it:

-In your sr2sieve folder, create a blank text file called sr2work.txt.
-Open the sr2work.txt file in a text editor, and put the following on the first line (without quotes): "318-320". Save the file.
-Start sr2sieve. This can be done either by navigating to the sr2sieve directory in a command box and running the command "sr2sieve", or by double-clicking sr2sieve.exe. Or, as Mini-Geek mentioned, you can run it from a batch file with the command "sr2sieve", but since there's no command line switches to specify, a batch file is really unnecessary.
-sr2sieve will open in a command window and run. To interrupt it press Ctrl-C, and sr2sieve will save its progress, and shut down. To resume it, just start it as you did before.
-When your range is done, sr2sieve will automatically exit. Please email the factors318.txt file to me (you already have my email address). If you want another range, possibly a larger one, just post here and I'll see what I can come up with. :smile:

Hope this helps!

Anon :smile:

Once again...my two cents:

I never use sr2work.txt. It's useless and creates more work and confusion. It was needed in older versions of sr2sieve but is no longer needed. If you were to sieve P=350G-360G, just specify at the command prompt or in a batch file:

sr2sieve -p 350e9 -P 360e9 -i (xxx)


No messing with additional files and you can always tell exactly what you're doing.


Gary

[B]318G-320G [/B]working :) Thank Anon!

Ok, so if I wanted to run it via command line, I would type
sr2sieve -p 318e9 -p 320e9
-i (xxx) <--- what is that part ?

53 factors, 6.0% done, ETA 19 Mar 03:18
Time here now is 18 Mar 21:11
So I guess I'm gonna need more work, and that's with Boinc/Rosetta and 3 eon clients all going at the same time. :)

[quote=gd_barnes;129136]Once again...my two cents:

I never use sr2work.txt. It's useless and creates more work and confusion. It was needed in older versions of sr2sieve but is no longer needed. If you were to sieve P=350G-360G, just specify at the command prompt or in a batch file:

sr2sieve -p 350e9 -P 360e9 -i (xxx)


No messing with additional files and you can always tell exactly what you're doing.


Gary[/quote]
Please note that even if you don't use sr2work.txt, you don't need to specify an input file with -i since I've named our sieve file sr2work.txt. :smile:

One of the main benefits of sr2work.txt, at least in my opinion, is the ability to queue up additional ranges so that you don't have to actually be at the console when one range finishes and another one needs to start. Of course, if you're just doing one big sieve, this is irrelevant, but for a distributed sieve, it can be useful. :smile:
[quote=IronBits;129142]53 factors, 6.0% done, ETA 19 Mar 03:18
Time here now is 18 Mar 21:11
So I guess I'm gonna need more work, and that's with Boinc/Rosetta and 3 eon clients all going at the same time. :)[/quote]
Okay, here's another range. You can add the following to sr2work.txt on a new line, sr2sieve will automatically start on it as soon as it's done with the first range:

[B]350G-384G[/B] (though of course you leave out the G's when you put it into sr2work.txt).

Enjoy! :smile:

[quote=Anonymous;129114]Aha, that's it. I remember reading that in order to get the timing to work with the multi-threading, Geoff had to switch it to using elapsed time--which unfortunately affects single-threaded mode as well as multi-threaded. :sad:[/quote]
It's basically righted itself since I posted first (now coming to 91596 p/sec). I was using the CPU somewhat heavily early in the test, so that the average was thrown off. The cpu_secs and elapsed_secs are indeed different, so it seems it's not completely just using elapsed time, but it seems they aren't large enough of a difference to be correct. Currently cpu_secs is 58632.125 and elapsed_secs is 61211.420. Strangely, 43 CPU minutes sounds about right.
[quote=Anonymous;129114]No, unfortunately the only way to get 64-bit speed increases is by running a 64-bit OS. Some virtualization software, such as qemu, can run 64-bit VM's on a 32-bit host OS, but they run reeeeaaaalllly sllllllooooow. Thus, if you want the 64-bit speed benefits, you have to run a 64-bit OS.[/quote]
Okay, I kind of figured that, just thought it was worth asking.

I'm going to finish this pretty quick (already 27% done :smile:), so I'd like another 40G range please. (Edit: was 20G, but my other core is freeing up in about 24 hours, and I want another 20G for that core)

[quote=Anonymous;129146][B]350-384[/B]
Enjoy! :smile:[/quote] Ok finished the first batch in 5 hours, just now adding the above. Let's see how long that goes :)

[quote=Mini-Geek;129162]It's basically righted itself since I posted first (now coming to 91596 p/sec). I was using the CPU somewhat heavily early in the test, so that the average was thrown off. The cpu_secs and elapsed_secs are indeed different, so it seems it's not completely just using elapsed time, but it seems they aren't large enough of a difference to be correct. Currently cpu_secs is 58632.125 and elapsed_secs is 61211.420. Strangely, 43 CPU minutes sounds about right.

Okay, I kind of figured that, just thought it was worth asking.

I'm going to finish this pretty quick (already 27% done :smile:), so I'd like another 40G range please. (Edit: was 20G, but my other core is freeing up in about 24 hours, and I want another 20G for that core)[/quote]
Because of the way the gaps are aligned, it will be easier for me to give you two separate ~20G ranges. Since you'd be splitting up a 40G range anyway for both cores, I'm guessing you won't mind:

[B]439G-460G
473G-495G[/B]

Enjoy! :smile:

[quote=Anonymous;129181]Because of the way the gaps are aligned, it will be easier for me to give you two separate ~20G ranges. Since you'd be splitting up a 40G range anyway for both cores, I'm guessing you won't mind:

[B]439G-460G
473G-495G[/B]

Enjoy! :smile:[/quote]
Yep, I don't mind. :smile:
If I add it to the end of sr2work.txt and restart sr2sieve it will automatically pick it up after finishing, correct?

[quote=Mini-Geek;129187]Yep, I don't mind. :smile:
If I add it to the end of sr2work.txt and restart sr2sieve it will automatically pick it up after finishing, correct?[/quote]
You don't even have to restart sr2sieve--it's designed so that you can queue up ranges in sr2work.txt even while sr2sieve is running. When sr2sieve finishes the one range it will automatically check sr2work.txt for more, and if there's more, it will immediately start on the next range. :smile: