I don't believe anyone has asked yet what your setting is for Minimum work buffer. If you've got it set to a high number, say 9 or 10 days, you might want to try reducing it, perhaps down to 1.

I mention that because, in the back of my mind, I have a vague recollection of someone else mentioning that a large work buffer number causes the project to think that your machine will take much longer to process the tasks it receives, and actually ends up sending it fewer tasks to ensure that deadlines will be met. Because your machines haven't established a usable APR for v7 CPU tasks, estimated run times will initially be vastly inflated to begin with. If a large work buffer number adds to those estimates, it's possible that the scheduler thinks that it simply has no tasks available that could possibly be completed by the expected deadline, rather than having no tasks available at all. That might be especially true when you have other projects sharing the CPU.

I had a minimum work buffer of 3 days. I've set it to 1 day (for both SETI@Home and Rosetta@Home), so I'll see if that helps. Thanks for the suggestion.

The work queue is a global setting instead of per project. So if you set a different value on different projects the last one will be the setting that you are using.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Calico,

One other thing I see, that was pointed out above, is that you have at least 3 possible 4 other projects running on those 2 machines. I can see the CPUs on both machines are being used by these other projects. Without getting too crazy on details, it may be that those other project are utilizing the CPUs so much that the manager doesn't request work from Seti. I tend to run at most 2 projects and turn off 1 while the other is running. In this case Seti is my primary. On my i5, I only run seti full time and it has both CPUs work units and GPU (this after I installed a relatively inexpensive graphic card). So, maybe just finish those other projects, then suspend and see if the manager will then download work units for the CPU, if it does then no need to go through a full reinstall.

I have had similar problems with trying to run Intel GPU tasks for Seti@home

With the latest version 7.2.39(x64) I can't run both CPU and GPU tasks at the same time. With the GPU enabled the BOINC manager fetches CPU and GPU tasks - the GPU tasks run but the CPU tasks just sit there doing nothing. If I suspend the GPU the CPU tasks start running straight away. If I then resume the GPU tasks the CPU tasks stop running and show 'Waiting to run' all cores at this stage show little usage.

CPU is i5-3570K

Any suggestions ?

---

Any suggestions ?

How much CPU do you reserve for each GPU WU?

---

I have had similar problems with trying to run Intel GPU tasks for Seti@home

With the latest version 7.2.39(x64) I can't run both CPU and GPU tasks at the same time. With the GPU enabled the BOINC manager fetches CPU and GPU tasks - the GPU tasks run but the CPU tasks just sit there doing nothing. If I suspend the GPU the CPU tasks start running straight away. If I then resume the GPU tasks the CPU tasks stop running and show 'Waiting to run' all cores at this stage show little usage.

CPU is i5-3570K

Any suggestions ?

When you had the CPU tasks running and resumed the GPU task were there any messages in the event log? Like "waiting for memory" or "waiting for GPU memory" maybe?
If you set Activity > Run Always & also Activity > Use GPU always do all of the tasks run?

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

It was 0.01 CPU for each GPU task.

As a test I was able to run another project CPU tasks at the same time Seti GPU tasks were running.

It was only Seti tasks that would not run on CPU when GPU tasks were running.

---

I have an i5-2600k with an NVIDIA GPU, an i5-3570 with Intel GPU only and an i7-3770k with Intel GPU only. ALL of them are running SETI CPU tasks with the GPUs running SETI as well (when work is available). I also run the Lunatics versions of SETI. Here is what I found works for me on my i7-3770k:

SETI@home preferences
Use CPU Yes
Use ATI GPU Yes
Use NVIDIA GPU Yes
Use Intel GPU Yes
Run only the selected applications SETI@home Enhanced: yes
SETI@home v7: yes
AstroPulse v6: yes
If no work for selected applications is available, accept work from other applications? yes
<-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><->

Under Activity on the toolbar:

Run based on preferences
Use GPU based on preferences
Network activity always available

<-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><->

Under Tools -> Computing preferences ->processor usage:

While computer is in use [checked]
Use GPU while computer is in use [checked]
On multiprocessor system, use at most 0.00%
Use at most 100% CPU time

<-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><->

app_config.xml contains:

<app_config>
<app>
<name>setiathome_v7</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>0.49</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>
</app_config>

<-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><->

app_info.xml contains:

<app_info>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.txt</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>setiathome_7.03_windows_intelx86__opencl_intel_gpu_sah.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r2061_windows_intel_gpu.cl</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>mb_cmdline-7.03-opencl_intel_gpu_sah.txt</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<coproc>
<type>intel_gpu</type>
<count>0.49</count>
</coproc>
<plan_class>opencl_intel_gpu_sah</plan_class>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.04</max_ncpus>
<file_ref>
<file_name>setiathome_7.03_windows_intelx86__opencl_intel_gpu_sah.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r2061_windows_intel_gpu.cl</file_name>
<open_name>MultiBeam_Kernels_r2061.cl</open_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline-7.03-opencl_intel_gpu_sah.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version> <app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.txt</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE_CPU_r1797.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE_CPU.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_intelx86</platform>
<cmdline></cmdline>
<file_ref>
<file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_x86_64</platform>
<cmdline></cmdline>
<file_ref>
<file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
</app_info>

<-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><-><->

NOTE WELL: I intentionally restrict SETI GPU to 1 at a time so that my Einstein GPU tasks run along side it. Einstein is also limited to 1 at a time. This way my Intel GPU runs 99-100% busy and I have 1 CPU feeding the GPU. There is about 60% of that CPU also available for everything else I run. As always, YMMV.

I hope this helps someone.

---

Well, just for something to try, I've (temporarily) set my "accept work from other applications" setting to No and in my client, I've temporarily set my other projects to "Won't accept new tasks". Now I see that there are a few AstroPulse tasks for SETI@Home in my task list. Thees are the first AstroPulse tasks I've seen since I started running BOINC again last weekend.

---

On my i5 machine, it's reporting no tasks are available

So, when you go to https://setiathome.berkeley.edu/prefs.php?subset=project, which venue (---, home, school, work) are you using, and what are your settings for:

Use CPU
Use ATI GPU
Use NVIDIA GPU
Use Intel GPU
Default computer location
Run only the selected applications
If no work for selected applications is available, accept work from other applications?

Ageless has a good point, I'd be interested in knowing this too..I can see the i5 has CPU work units but your i7 still doesn't, though the GPUs are working fine :) Are you listing them at different locations with different parameters?

Ageless has a good point, I'd be interested in knowing this too..I can see the i5 has CPU work units but your i7 still doesn't, though the GPUs are working fine :) Are you listing them at different locations with different parameters?

My i5 finally got some CPU units. Maybe it just needed some time. I don't yet have any separate parameters for different locations.

Recently I had tried temporarily disabling my setting my "Accept work from other applications" and setting the BOINC client on my i7 machine to not accept new tasks from other projects, and I got a few CPU AstroPulse tasks on my i7. Those took a very long time though - BOINC estimated they would take 24 hours, but they were finished (or stopped) after about 10-16 hours. My i5 machine has some SETI@Home v7 7.00 tasks running on its CPU that seem to be taking about 2 hours.

I'm thinking the lack of CPU tasks on my i7 might just be luck, or as others have said, due to scheduler decisions since I'm running other projects as well.

---