No AP being split..........

No Break Through Listen being split.............

MB work from last decade being reprocessed...............

Progress?

It's all progress, my friend.
Valid reasons for reprocessing the old work with the new apps.
Not sure what is up with the BLC stuff, I am still getting some.
Either it's cached in RTS, or still being split somehow behind the scenes.
AP is catch as catch can, until if and when Eric may decide to employ AP for BLC. Not sure when or if.

Meow.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I only got 8 out of yesterday's splitting (my time), but I've picked up 2 so far today from the latest file that is currently being split.

Cheers.

I think I got 2 AP's out of yesterday's split. I've received 19 so far from today's split.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

http://mikesworld.eu/download.html

Lunatics win32/64 0.45 Beta 6 is the most current one.
The stock application is more recent, but most of the improvements were to improve things on lower end hardware.

Thank You Grant, I'll run it and see what happens. Without Intel GPU

What happened to giving SoG another go?

---

Grant
Darwin NT

What happened to giving SoG another go?

I ran the installer from Mike's World eu on both rigs. Left the settings as recommended, did my usual tweak on the count to bring Nvidia GPU to 2. I did not invoke IGPU during installation. Both rigs have been running 24 hrs on the new installer with no SoGs being downloaded for processing.

Did I miss a step? Or are SoGs that rare?

---

"Sour Grapes make a bitter Whine." <(0)>

Did I miss a step? Or are SoGs that rare?

The problem is that you selected CUDA32, not SoG. So they're running even slower than they were with CUDA 50.
The CPU application is right, but not the GPU one. Re-run the installer, and double check to select the NVidia SoG application.
And i'd leave it set to run just 1 WU at a time. With higher end hardware some people have found it worth while, but for lower end hardware 1 WU at a time gives the most work per hour.

---

Grant
Darwin NT

http://mikesworld.eu/download.html

Lunatics win32/64 0.45 Beta 6 is the most current one.
The stock application is more recent, but most of the improvements were to improve things on lower end hardware.

Thank You Grant, I'll run it and see what happens. Without Intel GPU

What happened to giving SoG another go?

When running the installer DG you must select the GPU app that you want to run (unlike the CPU app which does get correctly selected) otherwise you get the oldest (and slowest) app by default (Cuda50 is the best Cuda app for your cards) and make sure that you reserve a CPU core to support the GPU task (or 2 cores if you're a heavy desktop user watching heaps of videos), but running 24/7 I'd expect at least a 10K RAC on your GTX660 rig (using it as a daily driver) and 8-9K RAC on the other (but I don't know your usage time).

Cheers.

I thought I recalled seeing a SoG setting in the previous installation but I guess I missed this time around. I'll rerun it.

---

"Sour Grapes make a bitter Whine." <(0)>

I thought I recalled seeing a SoG setting in the previous installation but I guess I missed this time around. I'll rerun it.

SoG is not a type of WU, oh Jaundiced one.
It is the application that you use to crunch with.
It processes both Arecibo and Guppi work.
So there is no SoG work to download.
Once you get it properly installed, you should see the app running in Task Manager.

Meow.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Thanks, after rerun I see one downloaded (Nvidia_opencl_SoG), So apparently it's working. Wait and see about the framing issue. I didn't remember that SoGs ran on the Nvidia GPU so limiting to 1 at a time makes sense and probably the invocation of 2 jobs is what caused the 'jerky' environment previously. One rig is my security camera server and a video stream intensive environment so that's where the framing should appear if it's gonna be a problem.

Again, thanks.

@Kittyman, I remembered seeing the SoG tag on WU's downloaded before in the Boinc tasks window, which is what I was referring to. I do see one now that I made the change.

---

"Sour Grapes make a bitter Whine." <(0)>

Make sure that -use_sleep is in your SoG command line. It will 'help' with the Seti work tying up other processes.
If it is still too problematic, there are other things you can do to minimize it.

Meow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

I do not see that call in the command line:

tt 1500 -hp -period_iterations_num 8 -high_perf -high_prec_timer -sbs 1024 -spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64

Where should it be inserted?

---

"Sour Grapes make a bitter Whine." <(0)>

I do not see that call in the command line:

tt 1500 -hp -period_iterations_num 8 -high_perf -high_prec_timer -sbs 1024 -spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64

Where should it be inserted?

Anywhere, does not matter.
In your case, probably easiest just to add it at the end.
Open the file with notepad, add a space, then add -use_sleep.
Save the file.
Like so..........
tt 1500 -hp -period_iterations_num 8 -high_perf -high_prec_timer -sbs 1024 -spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64 -use_sleep
The next task that starts with SoG should pick up the new command line and start using it.
Tasks already running will not be affected unless you shut down Boinc and restart it.

Meow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

-use_sleep added, Thanks again for the advice.
<(O)>

---

"Sour Grapes make a bitter Whine." <(0)>

-use_sleep added, Thanks again for the advice.
<(O)>

You are quite welcome. Hope it eases things up a bit for you.
Meow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

tt 1500 -hp -period_iterations_num 8 -high_perf -high_prec_timer -sbs 1024 -spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64

Let things run for a while.
If everything is good, try changing -period_iterations_num 8 to -period_iterations_num 5. Then 3, then 1 (or go straight to 1, and if things get too laggy, try 3, then 5).

EDIT- and same with the other system, try lower values of -period_iterations_num until things become too laggy, then go back to the last good value.

---

Grant
Darwin NT

And as so often is the case, there's a devil in the details:

I've looked in your results. You need to add a hyphen before the initial tt as well.

-tt 1500 -hp -period_iterations_num 8 ...etc

That should give you a line like this in the output from your results:

Target kernel sequence time set to 1500ms

As in one of my results (I use -tt 150):

...
Maximum single buffer size set to:2048MB
Number of period iterations for PulseFind set to:1
Target kernel sequence time set to 150ms
High-performance path selected. If GUI lags occur consider to remove -high_perf option from tuning line
SpikeFind FFT size threshold override set to:4096
...

---

Hyphen inserted, thanks.

---

"Sour Grapes make a bitter Whine." <(0)>

After getting a few resends I've managed to grab 6 fresh ones.

Cheers.

23 of them now.

Cheers.