JJSieve
 

Sorry if I'm asking a question already answered elsewhere :ermm:

I just put one of my boxes onto SOB:sieve and their download included JJSieve rather than proth_sieve that I have been using in the past for PSP:Sieve. I've noticed that JJSieve is consistently sieving at 635kp/sec compared to 615kp/sec
with proth_sieve, both using the SSE2 versions and using identical SOB.dat files. Is there any reason why I shouldn't use JJSieve? It uses slightly more ram (50mb as opposed to 35mb) but that isn't an issue with 4 gigs :lol:

Let me know if there is a reason why we can't use JJSieve, otherwise I'll be swapping over all my rigs over to JJSieve as the sobistrator is a great interface to use, even if just for PSP:Sieve.

Go ahead and use jjsieve.:smile:

Excellent, will be using it from now on, once I finish the few hundred G's I have left that is :)

One last question regarding JJSieve/SOB. I'm sieving ranges in the 1212xx G range, should I submit the factors that JJSieve pulls up to PSP:Sieve or are these ranges above/beyond what you guys will be looking at? see a few people have completed ranges in the 1000000 area but everything else is at/below 650000. Makes no sense to have someone else sieve a range that's already been sieved if the results are the same.

[QUOTE=Gomeler;103428]One last question regarding JJSieve/SOB. I'm sieving ranges in the 1212xx G range, should I submit the factors that JJSieve pulls up to PSP:Sieve or are these ranges above/beyond what you guys will be looking at? see a few people have completed ranges in the 1000000 area but everything else is at/below 650000. Makes no sense to have someone else sieve a range that's already been sieved if the results are the same.[/QUOTE]

The factors you find are dependent on the dat file you use, not the program.
If you want to benefit both SoB and PSP you would need to use the combined dat file. Now while you could use the combined dat file on the 1212xxx G range, this would cause a lot of extra work for HHH. The easiest thing would be to reserve the ranges here that are next in line in the sieve reservation thread.

Yup, using the combined DAT file, didn't think it was wise to just sieve for one and not the other. The reason why I ask is that the SOB automated reserveration system is distributing in the 1212xxx range while PSP is in the 500xxx range, I can't sieve SOB in the current PSP region but I'm still finding PSP factors. Should I just place the reservations in the reservation thread and submit the results when PSP gets down to 1212xxx? I'm just trying to milk my clockcycles for all they are worth and would hate to waste clockcycles :)

[QUOTE=Gomeler;103494] Should I just place the reservations in the reservation thread and submit the results when PSP gets down to 1212xxx? I'm just trying to milk my clockcycles for all they are worth and would hate to waste clockcycles :)[/QUOTE]
I would urge you to submit all your factors as soon as you find them. You could eliminate an LLR/PRP test or two and save a lot of clockcycles. HHH is going to have to chime in with what he wants to do about the reservations in the high range.

As far as "I can't sieve SOB in the current PSP region", I think that you are labouring under a misunderstanding. If you reserve in the current PSP region you will also be finding factors for SB. Most of these will be for n > 20M and so will not score immediately, but they will be accepted and eventually score.
You may also find factors for n < 20M. Take a look at the attached graph, and also the one in "Pretty Progress Pictures". The light blue points in the dark blue were found by the combined effort. For various reasons, they were missed in the original sieving of these ranges. Quite a few have even eliminated PRP tests for SB.

Thanks for the reply, I understand that w/ PSP combined sieving I'm finding SOB factors and I've been submitting my results to SOB:S but I needed slightly faster results, making a rush on the DC-Vault :) I'll inform Citrix of the ranges I have/will complete for SoB and submit the factors to PSP also.

It will be better if you inform 'hhh' and 'ltd' of the ranges.:smile: