How to report tasks immediately (needed for Boinc 6.12.34 and earlier):

Create, or edit an existing, cc_config.xml file in the Program Data folder for Boinc, using a text editor (Notepad),
- For Vista and Win7 create the file in this folder, C:\ProgramData\BOINC (this folder will likely be hidden, but should open if you type it into Explorer).

Add the following lines:

<cc_config>
<options>
<report_results_immediately>1</report_results_immediately>
</options>
</cc_config>

Using Multiple GPUs:
Depending on your driver, you may also need to add this line if you want to use multiple GPUs

<use_all_gpus>1</use_all_gpus>

Cache Levels (Additional Work Buffer):
For GPUGRID it is better to set a low cache level of say 0.05days (rather than use the default 0.25days).
Open Boinc in Advanced View, Click Advanced, Preferences, under the network usage Tab set the additional work buffer to a low value.
- This will optimise Work Unit turn around and expedite the project. It will also allow you to collect larger bonuses.

Using Multiple GPUs:
You may also need to add this line if you want to use multiple GPUs

<use_all_gpus>1</use_all_gpus>

I have heard that I should make app_info.xml file for GPUGRID and put these lines in it:
<coproc>
<count>0.5</count>
</coproc>

I don't know how to make it. Do you know? (It needs more than just those three lines.)

---

Report tasks immediately on Win XP:
Create the cc_config.xml file here,
C:\Documents and Settings\All Users\Application Data\BOINC\

Report tasks immediately on Vista or win 7:
Create the cc_config.xml file here,
C:\ProgramData\BOINC\

- details in first post -


Also,

You can add this Environmental System Variable to dedicate a CPU core for each GPU (just 1 thread for HT systems),
Variable name: Swan_Sync
Variable Value: 0

XP:
Start, right (alternate) click My Computer, Click Properties - Opens System Properties Window.
Click the Advanced Tab, then Environmental Variables.
Under System Variables, Click New,
For the Variable name type Swan_Sync
For the Variable Value type 0

Vista or Win7:
Start, right (alternate) click Computer, Click Properties - Opens System Window.
Click Advanced System Settings (left side), then Environmental Variables.
Under System Variables, Click New,
For the Variable name type Swan_Sync
For the Variable Value type 0

On Linux you need SWAN_SYNC=1

And for ubuntu?

I tried editing the file by typing:

sudo cp /etc/boinc-client/cc-config.xml /etc/boinc-client/backup_cc-config.xml

sudo gedit /etc/boinc-client/cc-config.xml 

included the line:

<report_results_immediately>1</report_results_immediately> 

in options like this

 <options>
   <report_results_immediately>1</report_results_immediately>
  </options> 

then saving and restarting boinc like this

sudo service boinc-client restart 

Is this right?

That looks about right to me (whatever that is worth).

You can tell if it is working if a project disappears as soon as it is 100% done, rather than the project hanging around with the message "ready to report results".

I just got this working in Ubuntu and I had a heck of a time with file ownership and permissions. I'm accustom to other Linux distros but I'm new to Ubuntu so I'm not familiar with how you level up in Ubuntu.

It seams to work and the average work done has raised a bit I think :D

You said:
For the Variable name type Swan_Sync
For the Variable Value type Swan_Sync=0

perhaps, you meant:
For the Variable name: Swan_Sync
For the Variable Value: 0

that way... it would put Swan_Sync=0 in environment
instead of

Swan_Sync=Swan_Sync=0

right?

You would think that (name, value) would be a more natural way of doing it, wouldn't you? I've been running with the whole "Swan_Sync=0" string in the value field ever since host 71413 went online.

This morning, I set the value to be 0: workunit 1490610 (reported 14:13:59) was relatively fast, but within the same range as pervious tasks.

Then I had another thought. Most programmers would use value "1" to activate an option, and "0" for the default setting. So I ran workunit 1491415 (reported 18:30:44) with variable Swan_Sync, value 1.

That run time of 14,588.31 seconds is at least 1,000 seconds faster than any previous run, including my only previous KASHIF_HIVPR_auto_spawn. Might be worth experimenting further.

You would think that (name, value) would be a more natural way of doing it, wouldn't you? I've been running with the whole "Swan_Sync=0" string in the value field ever since host 71413 went online.

This morning, I set the value to be 0: workunit 1490610 (reported 14:13:59) was relatively fast, but within the same range as pervious tasks.

Then I had another thought. Most programmers would use value "1" to activate an option, and "0" for the default setting. So I ran workunit 1491415 (reported 18:30:44) with variable Swan_Sync, value 1.

That run time of 14,588.31 seconds is at least 1,000 seconds faster than any previous run, including my only previous KASHIF_HIVPR_auto_spawn. Might be worth experimenting further.

Disclaimer: I'm a total noob and I don't know what I'm talking about...

On multi-core CPUs they start counting at zero so on a quad core you would have core 0, 1, 2, and 3 (instead of 1, 2, 3, 4).

I took swan-sync value "0" to mean [use core number "0"] (meaning core 1 to non-geeks). If I'm right swan-sync "1" would use core 2 etc.

Does anyone run a CPU monitor? If so you might see a different core being used as you cycle the numbers??

EDIT:

Evidently this is total nonsense (my understanding was incorrect).

See this post for an explanation of Swan_Sync:

http://www.gpugrid.net/forum_thread.php?id=2227&nowrap=true#18136

Value 1 on a TONI_HERGunb1 (workunit 1493006, same host as before) is back to the same sort of time as before. I'm about tested out for tonight: maybe tomorrow I'll try it with an empty value string, or even no variable at all, and see if it slows down - maybe just having anything at all there is good enough.

Ran workunit 1494710 with no environment variable at all - slightly slower, but nothing like the 20% - 30% envisaged by the original announcement.

From the text of that message, I think it's clear that the expected value is just 0

For Ubuntu:

From a Terminal goto the folder containing the cc_config.xml file by typing,

cd /etc/boinc-client/

Then backup the file by typing,

sudo cp /etc/boinc-client/cc_config.xml /etc/boinc-client/backup_cc_config.xml

Then edit the file by typing,

sudo gedit /etc/boinc-client/cc_config.xml

In options included the line:

<options>
<report_results_immediately>1</report_results_immediately>
</options>

then save and restart boinc,

sudo service boinc-client restart

---

I don’t think that swan_sync works for 6.03 tasks, (compiled for CUDA 2.2). It is there for CUDA 3 or above (the forthcoming 3.1 that might be 11% faster than CUDA 3.0, which is 30-35% slower than CUDA2.2 which does not work for Fermis, so this might even things out).
So it is most notably for Fermi, but note that it requires the cruncher to leave one CPU thread free per GPU, to fully benefit from the Environmental Variable.
If you wanted to use four GPU's a single CPU core is not enough (for all 4 GPUs), you need a Quad core CPU, or better.

I think the variable may work for the more recent 6.72 WU's but to a lesser extent. Either way, it should do soon (if/when these are compiled for CUDA 3.0, or more likely 3.1).
-
Swan_sync now works for the 6.12app and with non-Fermi cards as well as the 6.13app for Fermi cards or some pre-Fermi cards.

All my experiments with SWAN_SYNC in this thread relate to host 71413, which as you can see is an eight-core host (that's eight real cores, not HT semi-cores). I'm running seven BOINC CPU tasks plus one GPUGrid task on the single GTX 470 GPU. Obviously, Windows doesn't exactly run 'one task per core' - the thermal stresses would be horrendous if seven cores were generating maximum heat and the eighth was idle - but there should be plenty of spare cycles for the syncing.

If you look back at the announcement link from last time, you'll see that it is in the "GPUGRID and Fermi" thread. Also, it's clear from that announcement that the 20%-30% speedup I mentioned refers to a single application - by implication, v6.73 - with two modes of operation. That's what I'm failing to see.

I'm not sure where this idea come from, of a physical core ID being specified for the sync process - that goes against everything I've ever learned about multi-tasking operating systems - and it isn't supported by any post I can find from the project developers. But perhaps as you say we should wait for technical clarification.

It does not use one single CPU core, and on multi-GPU systems the CPU usage is spread out over all CPU cores, and controlled by the CPU, but overall 4 CPU cores will be used for a system with 4 GPU's.

L2B here...

Hello, I'm pretty new here, have been running Grid tasks for a few weeks and am looking for some feedback

I'm not currently getting any tasks, any ideas why not?

Currently running a pair of 465s, a i7-930 and the only thing overclocked are the fan settings on the GPUs!

Thanks

Ok...I'm back running Grid tasks...Brain fade on my part!

See previous post for my configuration.

It appears that I should be able to complete a ...dynamics 6.11 (cuda31) task in about 3.5 hours.

Does that seem sensible, given other's experience?

Thanks

Ok...I'm back running Grid tasks...Brain fade on my part!

See previous post for my configuration.

It appears that I should be able to complete a ...dynamics 6.11 (cuda31) task in about 3.5 hours.

Does that seem sensible, given other's experience?

Thanks

The tasks are different "sizes" so some take longer to run than others. Points awarded are typically higher for longer running tasks.

3.5 hours for a 6800 point work unit seems about right. Some work units will take about twice as long but they should also be worth about twice as much.

I'm not sure what the specific cause of it is but DO NOT USE THE SWAN_SYNC WITH PHYS-X DEDICATED TO THE CPU IF YOU ARE RUNNING VISTA 64-BIT. It causes Windows Explorer to continuously stop working and then restarts Explorer over and over in an infinite loop and is extremely difficult to maneuver to change the settings back because you only have about 8 seconds in-between Explorer crashes.

The more recent NVidia drivers are causing many GPUs to reduce their clock rates. So it is a good idea to make sure your cards Power management is set to Prefer Maximum Performance (NVidia control panel, Manage 3D settings, Power management mode).

I recommend that people crunching on Fermi cards control their fan speed using a tool such as EVGA Precision (now available without email registration). Typically these cards will run at up to 91 deg C. At such temperatures the task success rate drops. It is best to keep temperatures under 80deg C and under 70deg C if possible. Doing so will increase task success rates and the cards longevity.

To run GPUGrid tasks on a Fermi GPU find the app_info.xml file and include the following,

<app_info>
<coproc>
<type>CUDA</type>
<count>0.5</count>
</coproc>
</app_info>

I have added this into my W7 \program data\BOINC folder, but any explanation what it means/does to BOINC in general and GPUGRID specifically? Impact on other gpu projects? Other <coproc> flags documented?

Thanks