Probably as good a place as any-

Is there any one around that had been running the older stock or optimised CPU applications and is now running the new optimised application & making use of the AVX support?

Since upgrading from the old optimised application to the current v7 optimised with AVX supprt, my i7 2600 CPU is now running about 5°c hotter.

My AMD 8150 was normally running 24°-25° with the optimised SSE3 app. Now it's getting up to 27°-28° with the AVX app. I'm getting a little worried ;)

Using a Corsair h100

---

</Tazz>

Is there a clever way of freeing up one CPU core when the GPU is running an AP but when it is running MBs which do not need it? I do not want to loose 25% of my CPU RAC and cannot lways be present to baby sit the machine.

With your version of BOINC, you can do this with an app_config.xml file in your SETI data directory. Here's mine - set the gpu usage value to the values you need for your card. You don't need the max concurrent line - I use it to limit the number of AP's running at one time. Setting a value of one for the cpu usage will reserve one core but only while the AP task is running.


<app_config>
<app>
<name>astropulse_v6</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.06</cpu_usage>
</gpu_versions>
</app>
</app_config>

Now that it has been released, I am using the optimised app rather than stock to process APs on my GTX460. The above does not seem to work with the optimised app, presumably because optimised app does not use app_config? Is there an alternative way of achieving the same effect with optimised app? Probably by editing app_info instead?

---

Is there a clever way of freeing up one CPU core when the GPU is running an AP but when it is running MBs which do not need it? I do not want to loose 25% of my CPU RAC and cannot lways be present to baby sit the machine.

With your version of BOINC, you can do this with an app_config.xml file in your SETI data directory. Here's mine - set the gpu usage value to the values you need for your card. You don't need the max concurrent line - I use it to limit the number of AP's running at one time. Setting a value of one for the cpu usage will reserve one core but only while the AP task is running.


<app_config>
<app>
<name>astropulse_v6</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.06</cpu_usage>
</gpu_versions>
</app>
</app_config>

Now that it has been released, I am using the optimised app rather than stock to process APs on my GTX460. The above does not seem to work with the optimised app, presumably because optimised app does not use app_config? Is there an alternative way of achieving the same effect with optimised app? Probably by editing app_info instead?

You can of course edit app_info, but that's harder work.

In my experience, app_config can be used with app_info.xml, and app_config wins - it is read later than app_info when BOINC starts up, and if the same value is set in both, the one in app_config is used. I've certainly used AC's <gpu_usage> to over-ride AI's <count>. And the best bit of app_config is that it can be read (and re-read after editing) any time BOINC is running - take 'Read config file' from the Advanced menu.

There's one bug that I'm aware of, and it's cosmetic only. The GPU fraction in the task display - perhaps other values too - doesn't update immediately when the app_config file is re-read. But the number of running tasks does change straight away.

Is there a clever way of freeing up one CPU core when the GPU is running an AP but when it is running MBs which do not need it? I do not want to loose 25% of my CPU RAC and cannot lways be present to baby sit the machine.

With your version of BOINC, you can do this with an app_config.xml file in your SETI data directory. Here's mine - set the gpu usage value to the values you need for your card. You don't need the max concurrent line - I use it to limit the number of AP's running at one time. Setting a value of one for the cpu usage will reserve one core but only while the AP task is running.


<app_config>
<app>
<name>astropulse_v6</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.06</cpu_usage>
</gpu_versions>
</app>
</app_config>

Now that it has been released, I am using the optimised app rather than stock to process APs on my GTX460. The above does not seem to work with the optimised app, presumably because optimised app does not use app_config? Is there an alternative way of achieving the same effect with optimised app? Probably by editing app_info instead?

You can of course edit app_info, but that's harder work.

In my experience, app_config can be used with app_info.xml, and app_config wins - it is read later than app_info when BOINC starts up, and if the same value is set in both, the one in app_config is used. I've certainly used AC's <gpu_usage> to over-ride AI's <count>. And the best bit of app_config is that it can be read (and re-read after editing) any time BOINC is running - take 'Read config file' from the Advanced menu.

There's one bug that I'm aware of, and it's cosmetic only. The GPU fraction in the task display - perhaps other values too - doesn't update immediately when the app_config file is re-read. But the number of running tasks does change straight away.

OK got it working now thanks. turned out just to be a pesky typo!

---

Is there a clever way of freeing up one CPU core when the GPU is running an AP but when it is running MBs which do not need it? I do not want to loose 25% of my CPU RAC and cannot lways be present to baby sit the machine.

With your version of BOINC, you can do this with an app_config.xml file in your SETI data directory. Here's mine - set the gpu usage value to the values you need for your card. You don't need the max concurrent line - I use it to limit the number of AP's running at one time. Setting a value of one for the cpu usage will reserve one core but only while the AP task is running.


<app_config>
<app>
<name>astropulse_v6</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.06</cpu_usage>
</gpu_versions>
</app>
</app_config>

Now that it has been released, I am using the optimised app rather than stock to process APs on my GTX460. The above does not seem to work with the optimised app, presumably because optimised app does not use app_config? Is there an alternative way of achieving the same effect with optimised app? Probably by editing app_info instead?

You can of course edit app_info, but that's harder work.

In my experience, app_config can be used with app_info.xml, and app_config wins - it is read later than app_info when BOINC starts up, and if the same value is set in both, the one in app_config is used. I've certainly used AC's <gpu_usage> to over-ride AI's <count>. And the best bit of app_config is that it can be read (and re-read after editing) any time BOINC is running - take 'Read config file' from the Advanced menu.

There's one bug that I'm aware of, and it's cosmetic only. The GPU fraction in the task display - perhaps other values too - doesn't update immediately when the app_config file is re-read. But the number of running tasks does change straight away.

OK got it working now thanks. turned out just to be a pesky typo!

That will do it everytime.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

My AMD 8150 was normally running 24°-25° with the optimised SSE3 app. Now it's getting up to 27°-28° with the AVX app. I'm getting a little worried ;)

Using a Corsair h100

In my case it's gone from high 70°s to mid 80°s. Ambient temps in the low 30°s (it had been in the mid to high 30°s).
Still using the stock cooler, but with this bump in CPU temperature i've ordered a better basic after market heatsink & fan.

---

Grant
Darwin NT

My AMD 8150 was normally running 24°-25° with the optimised SSE3 app. Now it's getting up to 27°-28° with the AVX app. I'm getting a little worried ;)

Using a Corsair h100

In my case it's gone from high 70°s to mid 80°s. Ambient temps in the low 30°s (it had been in the mid to high 30°s).
Still using the stock cooler, but with this bump in CPU temperature i've ordered a better basic after market heatsink & fan.

I'm using a Corsair H70(Water Cooling) and My cpu temps while crunching stay at about 45°C, idle is about 29°C to 32°C, I plan on upgrading the cpu cooling to either a Thermaltake Water Pro 2.0 or a Thermaltake Water Extreme 2.0, depending on the case I'm using, My PC will have 4 closed loop cooling radiators, which means either an NZXT 630 or a Phantek Enthoo Primo case, at least as soon as I can get some 0.7mm thick thermal pads and some screws that is.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I'm using a Corsair H70(Water Cooling) and My cpu temps while crunching stay at about 45°C, idle is about 29°C to 32°C

I'm cheating a little with mine. My case is OLD with nowhere to mount a radiator, and being the cheapskate I am I made it work. It's always getting air from outside the case and keeping it outside the case.

---

</Tazz>

Is there a clever way of freeing up one CPU core when the GPU is running an AP but when it is running MBs which do not need it? I do not want to loose 25% of my CPU RAC and cannot lways be present to baby sit the machine.

With your version of BOINC, you can do this with an app_config.xml file in your SETI data directory. Here's mine - set the gpu usage value to the values you need for your card. You don't need the max concurrent line - I use it to limit the number of AP's running at one time. Setting a value of one for the cpu usage will reserve one core but only while the AP task is running.


<app_config>
<app>
<name>astropulse_v6</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>1.0</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>.33</gpu_usage>
<cpu_usage>.06</cpu_usage>
</gpu_versions>
</app>
</app_config>

Now that it has been released, I am using the optimised app rather than stock to process APs on my GTX460. The above does not seem to work with the optimised app, presumably because optimised app does not use app_config? Is there an alternative way of achieving the same effect with optimised app? Probably by editing app_info instead?

You can of course edit app_info, but that's harder work.

In my experience, app_config can be used with app_info.xml, and app_config wins - it is read later than app_info when BOINC starts up, and if the same value is set in both, the one in app_config is used. I've certainly used AC's <gpu_usage> to over-ride AI's <count>. And the best bit of app_config is that it can be read (and re-read after editing) any time BOINC is running - take 'Read config file' from the Advanced menu.

There's one bug that I'm aware of, and it's cosmetic only. The GPU fraction in the task display - perhaps other values too - doesn't update immediately when the app_config file is re-read. But the number of running tasks does change straight away.

Does high priority mode overrule this? Today I cannot get two APs to run simultaneously on my GTX460 even though 2 MB v7's run perfectly happily. Instead, 1 AP runs on the GTX460 and only uses 0.5 of the GPU (monitored by GPUz). However, the CPU cores are currently being used by another project (cosmology) and those WU's are running in high priority mode, mainly because I have CPU seti v7 WUs with exagerated run times as I have not yet returned 10, as the cosmology tasks have earlier due dates.

---

I'm using a Corsair H70(Water Cooling) and My cpu temps while crunching stay at about 45°C, idle is about 29°C to 32°C

I'm cheating a little with mine. My case is OLD with nowhere to mount a radiator, and being the cheapskate I am I made it work. It's always getting air from outside the case and keeping it outside the case.

Luv it.
The kitty farm is in similar state.
One makes do where one must.

The kitty crunching farm is nothing pretty......
All rigs side off, a bit of cooling fan tacked on here and there. Wires hanging out, things tucked in where they had to be.

It's all work, kids. Nothing pretty about it.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster