We have put the first WUs in the new acemd2 application.

I get:

Wed 10 Feb 2010 05:56:59 PM CET GPUGRID Starting task 594-IBUCH_1000smd_pYEEI_100202-3-10-RND9182_0 using acemd2 version 602

Are you expecting the 60% increase with this application/task set combo?

Exactly as the beta.

gdf

The "application" column in boinc manager is not relevant yet. What matters is the "messages" string. For now there are only a few WUs for the new app, more to come.

Old application,
Picked up these two tasks today,
5-GIANNI_BIND_751-81-100-RND2022
52-GIANNI_BIND_2-79-100-RND8818
Both use v6.71 (cuda23).
Although they say that they need 15% of one CPU each, they are actually only using about 1% between them. Tasks running on two GT240's on an i7-920 W7Pro X64, 7Threads enabled for CPU use, total CPU usage 88%. I freed up one thread to expedite the GPU tasks (the other 7 are crunching WCG tasks).
Are there many new application tasks compared to the older tasks?

It might be some consolation to others that my cards are getting the older, slower and wobblier tasks!

In project preferences you should be able to select the application.

gdf

OK, I know you mean:
Goto Your account, select GPUGrid Preferences, Select Edit GPUGrid Prefernces, and Deselect ACEMD - leaving ACEMD 2.

Thanks,

http://www.gpugrid.net/prefs.php?subset=project

I am also getting big performance improvements from my GTX260sp216:

21,804.53 3,627.96 4,531.91 6,118.08 ACEMD - GPU molecular dynamics v6.01 (cuda)
34,410.33 6,055.99 4,531.91 6,118.08 Full-atom molecular dynamics v6.71 (cuda23)
41,126.95 11,995.04 4,531.91 6,118.08 Full-atom molecular dynamics v6.71 (cuda23)

19,842.14 5,306.09 3,977.21 5,369.23 ACEMD - GPU molecular dynamics v6.01 (cuda)
26,610.25 5,641.57 3,977.21 5,369.23 Full-atom molecular dynamics v6.71 (cuda23)
26,838.32 5,967.80 3,977.21 5,369.23 Full-atom molecular dynamics v6.71 (cuda23)
42,542.30 12,353.83 4,531.91 4,531.91 Full-atom molecular dynamics v6.71 (cuda23)
40,984.92 12,257.39 4,531.91 4,531.91 Full-atom molecular dynamics v6.71 (cuda23)
33,375.15 7,349.85 2,882.39 3,891.23 Full-atom molecular dynamics v6.71 (cuda23)

Agreed, Well Done!
Some serious amount of improvement was achieved by refining the application.

Now seeing similar improvement on my GT240 cards:
1841813 1158304, 45,402.39 2,734.11 4,531.91 6,118.08 ACEMD - GPU molecular dynamics v6.01 (cuda)
1840137 1157154, 66,144.96 3,361.48 4,531.91 6,118.08 Full-atom molecular dynamics v6.71 (cuda23)

45,402.39s rather than 66,144.96s is a 45% GPU improvement.
CPU time also dropped by 23% on these CC1.2 cards.

I agree, and thanks for pointing that out.
The DDR5 cards performance increased by about 55% with the new application, whereas the DDR3 based cards only increased by about 45%.
When you do all the maths the DDR5 cards work out at being about 15% faster than the DDR3 cards, everything else being equal.

Of course the purchase costs can be different too, so it is worth shopping around within your budget for the correct card. It is also worth noting that some GT220 cards actually cost as much as the lesser GT240 cards, but will certainly not perform anywhere near as well. At the present time the GT240s offer the best value for money, by some way, but even within the GT240 range there are some bargains!

There is a lot of variation with these GT 240 cards:

RAM can be DDR3 or DDR5 - note the 15% performance gain from DDR5 and work out if it is worth the extra cost.

RAM can be anywhere from 512MB up to 2GB (but this makes no difference here)! So dont pay any extra for More RAM!

Shader count is generally 96, but not always! There are a few GT240's that have more (112, I think) - they are harder to find and tend to cost more. If you find one with DDR5 and good clocks, it should outperform a GTS250, and cost a fair bit less, both in terms of the initial purchase cost and especially the running costs (about 65W vs 160W +/- 30W depending on the Manufacturers)!

Clocks - well there are many factory flavours! Obviously the higher the better, but if you are into overclocking, what they have already done is what you cant do.

Sorry, it was a few weeks ago that I cam accross it. I thought it was a misprint so I looked into it, but I thought it was genuine after researching it. Just have not managed to find an inexpensive one yet.
The only GTS240 I had, did not work - avoid at all cost!!!

There are no tasks in the ACEMD 2 queue.

New smaller revisions for acemd ver 2 are out. 6.03/6.04.
The Linux application should work better, for Windows we just fixed a minor issue on some input files.

gdf

Just had my first task failure (across three 9800GT-class GPUs) since the new app (v6.03) was released. I've mostly been allocated GIANNI_BIND, but this was an OTTO_HERG:

SWAN : FATAL : Failure executing kernel sync [frc_sum_kernel] [700]
Assertion failed: 0, file ../swan/swanlib_nv.cpp, line 203

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

So here I am ;-)

go to your project preferencs.

gdf

Deselect (remove box tick for) ACEMD


It is confusing that the tasks are called,
Full-atom molecular dynamics v6.71 (cuda23) and ACEMD - GPU molecular dynamics v6.03 (cuda).

While the respective projects are called,
ACEMD and ACEMD ver 2.0.

Full-atom molecular dynamics v6.71 (cuda23) uses ACEMD
ACEMD - GPU molecular dynamics v6.03 (cuda) uses ACEMD ver 2.0

In practice select only:
ACEMD ver 2.0

The old application will be on until we have finished the old tasks.
gdf

Palmss, you probably need to update your driver.

MrS
____________
Scanning for our furry friends since Jan 2002

The nomenclature is wanting, as is the application version numbering system, however it will simplify soon; we are presently using up the last of the old tasks. So very shortly we will only be left with the (Up to 60% faster) ACEMD - GPU molecular dynamics tasks (ACEMD ver 2.0), and occasional Beta work.

What is the minimum CUDA/driver version Required to run these New tasks?


PS. A few days ago I did get one error on a GT240 (SWAN: FATAL : swanMalloc failed). It is very rare that I get any errors on these devices; but it was application version 6.01.
I am now using NVidia’s most up to date Beta and overclocking five GT240s with no problems.

Name3-GIANNI_BIND_650-79-100-RND5157_0 Workunit1170404 Created16 Feb 2010 9:20:51 UTC Sent16 Feb 2010 9:20:51 UTC Received16 Feb 2010 18:05:49 UTC Server stateOver OutcomeClient error Client stateCompute error Exit status-40 (0xffffffffffffffd8) Computer ID63357 Report deadline21 Feb 2010 9:20:51 UTC Run time16100.420681 CPU time1031.166 stderr out
<core_client_version>6.10.18</core_client_version>
<![CDATA[
<message>
- exit code -40 (0xffffffd8)
</message>
<stderr_txt>
# There are 2 devices supporting CUDA
# Device 0: "GeForce GT 240"
# Clock rate: 1.53 GHz
# Total amount of global memory: 536870912 bytes
# Number of multiprocessors: 12
# Number of cores: 96
# Device 1: "GeForce GT 240"
# Clock rate: 1.53 GHz
# Total amount of global memory: 536870912 bytes
# Number of multiprocessors: 12
# Number of cores: 96
MDIO ERROR: cannot open file "restart.coor"
# There are 2 devices supporting CUDA
# Device 0: "GeForce GT 240"
# Clock rate: 1.53 GHz
# Total amount of global memory: 536870912 bytes
# Number of multiprocessors: 12
# Number of cores: 96
# Device 1: "GeForce GT 240"
# Clock rate: 1.53 GHz
# Total amount of global memory: 536870912 bytes
# Number of multiprocessors: 12
# Number of cores: 96
# There are 2 devices supporting CUDA
# Device 0: "GeForce GT 240"
# Clock rate: 1.53 GHz
# Total amount of global memory: 536870912 bytes
# Number of multiprocessors: 12
# Number of cores: 96
# Device 1: "GeForce GT 240"
# Clock rate: 1.53 GHz
# Total amount of global memory: 536870912 bytes
# Number of multiprocessors: 12
# Number of cores: 96
SWAN: FATAL : swanMalloc failed