You don't need <user_friendly_name>, but you might need a <plan_class>.

Have a check in the documentation.

I am going to check it locally as well.

gdf

I tested the former 6.05 windows-application with an app_info file and the result is fine: p9-IBUCH_1_opt01_pYEEI_101027-4-20-RND8089_0
and the speed is as it was before the version change.

The BOINC client behaviour is still a bit strange, because the app_info.xml isn't perfect. I will test this further.
Can you or skgiven tell me what are the right dll's to use with v6.05.

I think it’s down to the Scientists/Techs to determine and use the best app and driver combos available for the present ranges of GPUs, even if it means using the older apps, and I don't appreciate investing in Fermi's only to see them run at 50% GPU Utilization, when they could be and have been running at 98%.

I see little point in crunchers overclocking and optimising their input only to have their contribution crippled by being forced to use poor app/driver combos. So to spend time trying to DIY an app that we already had makes little sense.

Here I found an old app_info.xml from Collatz (which imho has even more useless science than DNETC):

While the value of DNETC may in question, I think it's short sighted to discount research projects like Collatz that deal with math theory. Without the advances in mathematics over the last centuries modern science would be impossible. Added to that Collatz is IMO one of the best run distributed projects around. Maintained primarily by one person (with a little help from his friends) it was largely responsible for getting ATI GPUs natively integrated into BOINC. Many platforms are supported. The clients are rock solid. Client upgrades are actually upgrades and the changes are fully explained. Project communication is amazing and problems are dealt with quickly. Those who prefer other types of research don't have to run it. Math science aside, as a model of a well run project it earns accolades.

So to spend time trying to DIY an app that we already had makes little sense.

As much as I agree that the science team has to deliver some runnable apps, in the meantime while they sent out not runnable apps and have good ones still in stock just not delivered, it's a better utilisation of my GPU as the current set-up with another project of dubious benefit.

As long as the the current app is sent to clients it's a giant waste of resources, and everything that helps to contain that waste has to be considered "good".

Edith says some OT things ;)
I think there are good mathematical projects a) possible and b) already running, and I think there are worse project benefit-wise than DNETC and Collatz, every single Primeproject is imho definitely worse ;) But unfortunately for my GT240 there are no much other projects available under Linux.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

I have uncovered the reason why Linux version 6.12 is running so slow. I figured out how to get the GPU utilization.

$ nvidia-smi -a -l

This shows that the GPU utilization fluctuates between 2% and 40%. This explains very well why it is taking four times longer.

The new Windows 6.12(cuda) application is (several times stated in this thread)
not performing as well as the older 6.05 version. On my GT240 runtimes are about
10% longer and the new application uses 25% more CPU-time.

Disclaimer: Use this on your on risk

For Windows users, with a single card (from the G200-series), who wants to run the better performing 6.05 version you need following files:

acemd2_6.05_windows_intelx86__cuda.exe
app_info.xml
cudart.dll
cufft.dll
logops3grid.png
project_1.png
project_2.png
project_3.png
slideshow_cellmd_00
slideshow_cellmd_01
slideshow_cellmd_02
slideshow_ga_00
slideshow_ga_01
slideshow_ga_02
stat_icon
tcl85.dll

Procedure:

1. If you are out of work, detach from GPUGRID.
2. Create under projects the www.gpugrid.net directory.
3. Copy above files into that directory.
4. Attach to GPUGRID again.

I didn't have experience until now what is happening if new work is requested when a GPUGRID task is running.

Contents of app_info.xml:

<app_info>
<app>
<name>acemd2</name>
</app>
<file_info>
<name>acemd2_6.05_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>acemd2</app_name>
<version_num>605</version_num>
<plan_class>cuda</plan_class>
<avg_ncpus>0.260000</avg_ncpus>
<max_ncpus>0.260000</max_ncpus>
<flops>2923397447.700002</flops>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>acemd2_6.05_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

The new Windows 6.12(cuda) application is (several times stated in this thread)
not performing as well as the older 6.05 version. On my GT240 runtimes are about
10% longer and the new application uses 25% more CPU-time.

Disclaimer: Use this on your on risk

For Windows users, with a single card (from the G200-series), who wants to run the better performing 6.05 version you need following files:

acemd2_6.05_windows_intelx86__cuda.exe
cudart.dll
cufft.dll
tcl85.dll
....

If you need those three DLLs (away from my rigs at the moment, can't check directly), then they should be referenced in app_info.xml - twice each, once as <file_info>, marked </executable> like the main program is, and again as a <file_ref> in the app_version> section. You don't need to worry about that for the eye-candy files.

I have uncovered the reason why Linux version 6.12 is running so slow. I figured out how to get the GPU utilization.

$ nvidia-smi -a -l

This shows that the GPU utilization fluctuates between 2% and 40%. This explains very well why it is taking four times longer.

And the old one took 1 complete CPU core, now it's running on the CPU as claimed in the description (0.15CPU+1GPU) but never did in reality.

Any comments about my proposed app_info?

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Richard wrote:

If you need those three DLLs (away from my rigs at the moment, can't check directly), then they should be referenced in app_info.xml - twice each, once as <file_info>, marked </executable> like the main program is, and again as a <file_ref> in the app_version> section. You don't need to worry about that for the eye-candy files.

I know the other files aren't needed really and would be downloaded from the server.
As I described, without the dll's in the app_info, it's working now.

I tried with the dll's in the app_info file, but after starting the boinc-client they disappeared immediately. The main program needs the dll's.
Probably I put them only once in the app_info. After I'm sure that requesting new work and starting the new task is functioning well, I'll try your proposal.

As long as the the current app is sent to clients it's a giant waste of resources, and everything that helps to contain that waste has to be considered "good".

There is one thing you can do to speed up crunching a little bit ( ~10% )
http://www.gpugrid.net/workunit.php?wuid=2043240
This wu was crunched with default setting
http://www.gpugrid.net/workunit.php?wuid=2044504
http://www.gpugrid.net/workunit.php?wuid=2044547
These two did run together with the setting 0.5 GPU's (done in client_state.xml)
Should be working with an app_info, setting <count>0.5</count>
GPU-usage increased from ~65% to ~79% (Afterburner)
Memory-usage was ~760MB (hard on limit!)
I'll check it tomorrow with the app_info, it's too late now for me.
Alexander

Looks good at the moment.





mem-usage ~605MB

Looks good at the moment.





mem-usage ~605MB

WUprop with nci, sweet.
Can it wotk side by side with freehal, or is the boinc manager limited to just one nci project?

WUprop with nci, sweet.
Can it wotk side by side with freehal, or is the boinc manager limited to just one nci project?

Sorry, no idea!
I found a hint in a forum (planet3D???), they are collecting statistical data, cpu-load is very low, so why not?
Alexander

WUprop with nci, sweet.
Can it wotk side by side with freehal, or is the boinc manager limited to just one nci project?

It can work with as much nci-projects as are available, currently WUProp and QCN, only FreeHAL ain't one, it's just a CPU-intensive project with lots of useless pauses.

Edith says:
Of course most GPU projects are nci-projects as well.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Richard wrote:

If you need those three DLLs (away from my rigs at the moment, can't check directly), then they should be referenced in app_info.xml - twice each, once as <file_info>, marked </executable> like the main program is, and again as a <file_ref> in the app_version> section. You don't need to worry about that for the eye-candy files.

I know the other files aren't needed really and would be downloaded from the server.
As I described, without the dll's in the app_info, it's working now.

I tried with the dll's in the app_info file, but after starting the boinc-client they disappeared immediately. The main program needs the dll's.
Probably I put them only once in the app_info. After I'm sure that requesting new work and starting the new task is functioning well, I'll try your proposal.

My former setup with v6.05 and an app_info.xml was working well.
For correctness I changed my app_info.xml into:

<app_info>
<app>
<name>acemd2</name>
</app>
<file_info>
<name>acemd2_6.05_windows_intelx86__cuda.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>tcl85.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>acemd2</app_name>
<version_num>605</version_num>
<plan_class>cuda</plan_class>
<avg_ncpus>0.260000</avg_ncpus>
<max_ncpus>0.260000</max_ncpus>
<flops>2923397447.700002</flops>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>acemd2_6.05_windows_intelx86__cuda.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>tcl85.dll</file_name>
</file_ref>
</app_version>
</app_info>

Any news from the project team?
Why is there still the rubbish app available?
Are they not interested in a usable one?
The treatment we get from them feels like a kick in the gut.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Yes, I get annoyed too. We have to remember this is a small team with limited resources and time constraints. To reconfigure the server with the old app and work on a replacement might take more time than just working on the replacement app and uploading that when it’s ready. GDF said they are looking into the problems and hope to see something out this week.

Good Luck,

They just have to reinstall the 6.04 again, no real rocket science. Keeping that completely broken stuff online for even an hour longer is wilful neglect and making the middle finger curse to us.

If they let those alpha-stuff loose on unsuspecting non-testers they have to take it back asap after it's clear it's not working. and that's clear since a whole week.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

this is just a waste of time as the new workunits will not work on old applications.

gdf

Richard wrote:

If you need those three DLLs (away from my rigs at the moment, can't check directly), then they should be referenced in app_info.xml - twice each, once as , marked like the main program is, and again as a in the app_version> section. You don't need to worry about that for the eye-candy files.

I know the other files aren't needed really and would be downloaded from the server.
As I described, without the dll's in the app_info, it's working now.

I tried with the dll's in the app_info file, but after starting the boinc-client they disappeared immediately. The main program needs the dll's.
Probably I put them only once in the app_info. After I'm sure that requesting new work and starting the new task is functioning well, I'll try your proposal.

My former setup with v6.05 and an app_info.xml was working well.
For correctness I changed my app_info.xml into:



acemd2


acemd2_6.05_windows_intelx86__cuda.exe



cudart.dll



cufft.dll



tcl85.dll



acemd2
605
cuda
0.260000
0.260000
2923397447.700002

CUDA
1


acemd2_6.05_windows_intelx86__cuda.exe



cudart.dll


cufft.dll


tcl85.dll