[QUOTE=henryzz;335418]I don't think multithreading is possible on windows.
From memory it uses pthreads which I think is officially linux only. It does seem to be possible to build on win32 now and there seem to be claims of having it working for 64-bit. You would have to compile sr1sieve yourself to take advantage of this on windows.[/QUOTE]

I build with mingw, not cygwin. I believe that pthreads exist in cygwin, but not mingw.

[QUOTE=rogue;335423]I build with mingw, not cygwin. I believe that pthreads exist in cygwin, but not mingw.[/QUOTE]
[url]http://sourceforge.net/apps/trac/mingw-w64/wiki/Compile%20pthreads[/url]
This is the link I came across. That is mingw-w64.

To simulate multithreads option can I on my I7 ( HT on) open 8 cmd windows and in each one put sr2sieve -i sr_10.abcd -pxx -Pxxx
and than distribute range xx-xxx and after process is over join all factors and then remove it from abcd file?

[QUOTE=pepi37;335452]To simulate multithreads option can I on my I7 ( HT on) open 8 cmd windows and in each one put sr2sieve -i sr_10.abcd -pxx -Pxxx
and than distribute range xx-xxx and after process is over join all factors and then remove it from abcd file?[/QUOTE]
That is the standard method. srfile is used to remove the factors in factors.txt.

WOW :)
You can tell me whatever you wont, but this is discovery for me: with 12 cores ( 4+4, and 4) on second CPU I am capable of doing much deeper sieving in fraction of time :) I was "afraid" how will ABCD file tolerate to be accesed from few process in same time, but my fear is / was unnecessary
And much deeper sieve is less llr-ing :)
P.S It looks like that in this method must be same number of directories as cores: if you run if from same directory only last sieve process write checkpoint:and that is not practical in case of lets say power failure...

[QUOTE=pepi37;335452]To simulate multithreads option can I on my I7 ( HT on) open 8 cmd windows and in each one put sr2sieve -i sr_10.abcd -pxx -Pxxx
and than distribute range xx-xxx and after process is over join all factors and then remove it from abcd file?[/QUOTE]

I use Console2. One window, eight tabs with a command prompt.

Running multiple instances in one directory can result in the messing up of checkpoint files because all instances try to write to the same checkpoint file. At least under Linux that's the case. Don't know about windows. That's why I run every instance in a seperate directory.

I should add that I stop and restart very often because I need the machines for work during the day. If you finish in one go it's probably no problem.

[QUOTE=rogue;335465]I use Console2. One window, eight tabs with a command prompt.[/QUOTE]
Great tip- very useful info! I immidiatelly start to use it on LLR :)

[QUOTE=Puzzle-Peter;335505]Running multiple instances in one directory can result in the messing up of checkpoint files because all instances try to write to the same checkpoint file. At least under Linux that's the case. Don't know about windows. That's why I run every instance in a seperate directory.

I should add that I stop and restart very often because I need the machines for work during the day. If you finish in one go it's probably no problem.[/QUOTE]

I noticed this, but was small test sieve.
No I was running from different directories :)

I wish there was a way that I could automatically run the sieve with a batch file that does all of the ranges for you.

An algorithm something like this:

○ Console opens
○ Input range increment, start, end, number of cores to run on
○ Split sieve work
○ Start instances of sieve[INDENT]○ Read from file in arbitrary location via temp file?[/INDENT][INDENT]○ Output to console with state of combined sieve every 60 sec.[/INDENT]
Something like this could work quite well, I think. Would this be difficult to program, or is it a trivial task? The instances could be started via a customized batch file or something like that.

Thoughts?

Can someone explain better what is this options for?

-B --baby METHOD Use METHOD for baby step mulmods.
-G --giant METHOD Use METHOD for giant step mulmods.
--ladder METHOD Use METHOD for ladder mulmods.

Is any of those methods faster or slower ( and in what cases)?