All have the Deadline of 4/04/2015

"C:\Program Files\BOINC\boinccmd" --project http://asteroidsathome.net/boinc update

<config>
	<refresh>
		<downloads>	1709	</downloads>
		<uploads>	1307	</uploads>
		<refresh>	3571	</refresh>
		<refresh_asap>	1399	</refresh_asap>
	</refresh>
</config>

I will try resetting the project if I see 34 failed downloads & nothing running.

Anyone got a way to get new work and avoid this d/l problem?

222 download errors in the last 2 days on 102.10 SSE2 app.

Maybe he needs a lesson in PR, ...

The only way I have found to configure for SSE2 work (and exclude SSE3 and AVX versions for CPU) is via an app_info.xml file

... a discussion of the boinc "resource share" performance.
I wish it were simply based on execution times but I have read that it is based on estimated credit production.

<app_info>
  <app>
    <name>period_search</name>
    <user_friendly_name>Asteroids</user_friendly_name>
  </app>
  <file_info>
    <name>period_search_10210_x86_64-pc-linux-gnu__sse2</name>
    <executable/>
  </file_info>
  <app_version>
    <app_name>period_search</app_name>
    <version_num>1021</version_num>
    <avg_ncpus>1.00</avg_ncpus>
    <max_ncpus>1.00</max_ncpus>
    <plan_class>sse2</plan_class>
    <file_ref>
      <file_name>period_search_10210_x86_64-pc-linux-gnu__sse2</file_name>
      <main_program/>
    </file_ref>
  </app_version>
</app_info>

<app_info>

  <app>
    <name>period_search</name>
    <user_friendly_name>Asteroids</user_friendly_name>
  </app>

  <file_info>
    <name>period_search_10210_x86_64-pc-linux-gnu__sse2</name>
    <executable/>
  </file_info>

  <app_version>
    <app_name>period_search</app_name>
    <version_num>10210</version_num>
    <avg_ncpus>1.00</avg_ncpus>
    <max_ncpus>1.00</max_ncpus>
    <plan_class>sse2</plan_class>
    <file_ref>
      <file_name>period_search_10210_x86_64-pc-linux-gnu__sse2</file_name>
      <main_program/>
    </file_ref>
  </app_version>

  <app_version>
    <app_name>period_search</app_name>
    <version_num>1021</version_num>
    <avg_ncpus>1.00</avg_ncpus>
    <max_ncpus>1.00</max_ncpus>
    <plan_class>sse2</plan_class>
    <file_ref>
      <file_name>period_search_10210_x86_64-pc-linux-gnu__sse2</file_name>
      <main_program/>
    </file_ref>
  </app_version>

</app_info>

but was using just one CPU core + the GPU

Do I infer that boinc does not manage the CPU and GPU work buffers separately?

... keep the "minimum" buffer size small, especially on projects, such as A@H

All this far exceeds the 10% resource share assigned to the project.

... if A@H high priority will really use all cores

it was observed that a "3 day" value led to a download of 160 work units

on the assumption that boinc 7.2.42 really means keep a "minimum buffer" of x days

There are 151 tasks in the buffer already (a mix of CPU and GPU)
...
But first I want to see if boinc will force that issue as deadlines loom.

I found that running more than 1 A@H task caused the new CPU to run at over 38C

One more question --- Assuming we get Asteroids to give CPU (and GPU) work, is there a way to allow only sse2 work and exclude the sse3 and avx types which run more slowly on my specific CPU chip?

I don't know how useful, or relevant, the following numbers might be. Here are the reported Gflops (-> computer -> details -> application details )
cuda55 166 Gflops
avx 112 Gflops
sse3 156 Gflops
sse2 188 Gflops
...
**Still curious why Asteroids prefers the sse3 (CPU) over sse2 ??

<app_info> 


    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application SSE3</user_friendly_name>
    </app>

    <file_info>
        <name>period_search_10210_windows_intelx86__sse3.exe</name>
        <executable/>
    </file_info>

    <app_version>
        <app_name>period_search</app_name>
        <version_num>10210</version_num>
        <file_ref>
            <file_name>period_search_10210_windows_intelx86__sse3.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>


</app_info> 

i can never download enough tasks to keep the server busy.

As requested, here are the first lines of the Event Log from the most recent restart of boinc manager and boinc client

I usually have about 100 projects if not more running/waiting ...

If you have a "100 projects" lined up then your server should NEVER be out of work ...

I have no idea what ultimately happens to these WUs that max out on errors ...

The units just get recycled and resent to someone else, it's not really a problem as the Server does it all automatically.

Part of your problem with not getting any units is that the project was OUT of them for a few days, are you getting them again now?

What does this mean?