p115-IBUCH_1_pYEEI_101109-9-20-RND4744_0 took this:
Run time 95757.294388
CPU time 3680.72
Claimed credit 7954.42

An old IBuch from before the big mess with the new sloppy crap of an app had this (p30-IBUCH_8_pYEEI_101027-3-4-RND5091_0):
Run time 61218,70
CPU time 59819,61
Claimed credit 7954.42

So an increase of ~50% in crunch time.


My last completed Kashif:
53-KASHIF_HIVPR_n1_bound_so_ba1-70-100-RND8429_1
Run time 138546.228961
CPU time 1301.94
Claimed credit 6409.23

One of the same type from before the mess (264-KASHIF_HIVPR_n1_bound_so_ba1-34-100-RND1335_1):
Run time 54414,69
CPU time 53990,94
Claimed credit 6409.23

Crunch time has tripled.


The only Toni so far:
input_r199s1-TONI_MSM5-2-4-RND9936_1
Run time 45747.43243
CPU time 2241.32
Claimed credit 3539.96

I have none with the same amount of claimed credits, thus no same type.
The shortest one was this (S50-TONI_HERGMETAXDOFE-22-50-RND4899_1):
Run time 49040,07
CPU time 48419,91
Claimed credit 5764,79

Rt/Cc old: 8,51
Rt/Cc new: 12,93

Crunch time has increased by ~50%

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

If your're using ubuntu and install boinc thru apt-get, then export SWAN_SYNC=0 would not work by default. boinc client is run by user "boinc" whc cannot see the env var you set on your account.

Workaround is:
stop the client
edit /etc/default/boinc-client
change BOINC_USER to root
sudo -i
export SWAN_SYNC=0
start the client

Best Method:
edit /etc/enviroment -> in windows, this is the system env var
then add SWAN_SYNC=0

To verify:
echo $SWAN_SYNC

It should output 0

---

Thanks X-Files 27, thanks & done. Now back to hope.

BTW I've read that many were against running boinc as root, which is understandable being a DC Project. But I've got nothing in my PCs, they're just crunchboxes to me & this is just a hobby.

---

To verify:
echo $SWAN_SYNC

It should output 0

As this answer is the one on my machine, it seems to be that despite the many non-helpful half-answers I got here it may have worked nevertheless.

The crunch time has worsened despite that big time, as you can see in my last post. If the new app does more than double the science than the old one, it's just that you can ditch the next generation of cards because of excessive demands by this project, if not, it's just crap.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

The 6.13app is slow for GT240's, on Windows and Linux. It seems to work as well with the CC1.3 cards, but not the CC1.2 cards. Use an older driver and run the 6.12app.

The 6.13app is slow for GT240's, on Windows and Linux. It seems to work as well with the CC1.3 cards, but not the CC1.2 cards. Use an older driver and run the 6.12app.

So I have to downgrade my system to something inferior to suite the sloppy programming of the app? And for weeks you tried to persuade me to upgrade my old driver, fiddle around in some dubious innards of my core system or whatever SWAN_SYNC does, so I could run your so much better new app, and now you slap me in the face and say: F*** off with your current drivers, get back the outdates stuff or bugger off. Very fine behaviour indeed.

If you weren't the only available project for my system with a valid and good science I could not get away here fast enough.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Hi Saenger,

While I understand your frustration, BOINC computing for GPU just is not as easy we all would like it to be. There are many variables involved between the apps the project creates, the drivers NVIDIA publishes, each GPU family, and BOINC itself. It's complicated, that's just how it is, and this project is still officially listed as a beta project. GDF and team, along with volunteers here on the forum are trying their best. If this is the only project you deem worthwile for your NVIDIA card and you want to participate then you might consider accepting the project defaults, like the recent decision to use less CPU which does run slower overall, or you could learn a little *nerd* to get the most crunching from your equipment. While askign questions and engaging in a vigorous discussion is welcome I would like remind you of the forum posting rules which in part state: "No messages that are deliberately hostile or insulting."

---

Thanks - Steve

Even I can relate with Saenger's frustration. It's not fun to have something work, & then "not" work, because of optimizations & improvements gone bad. Whether you're MS or Apple, if something goes wrong, you'll get a million thumbs down & that kid from Springfield who always says "Ha, ha!"

I myself DO want my PCs to die. But I want them all to die a natural & noble death. I'd have to cheat someone or cheat myself, if I wanted to do a complete overhaul of my GPUs. So unless Nvidia is paying you to care about their GPU sales, please still consider the people with all the old stuff. ;-)

---

I can just say that we have changed the way the application works in Linux because some users complained on the use of a CPU.
Now some others complains because the GPU is not used well enough.

As I said in a previous post, we are making the GPU utilization mode a project variable, so that you can set it in a easier way from Linux and from Windows.
It just requires some time.

gdf

I can just say that we have changed the way the application works in Linux because some users complained on the use of a CPU.
Now some others complains because the GPU is not used well enough.

As I said in a previous post, we are making the GPU utilization mode a project variable, so that you can set it in a easier way from Linux and from Windows.
It just requires some time.

gdf

I was one who complained about the secret use of the CPU for the project, I had absolutely no complaints about the use of it in general. The only bad part was that the app unnecessary pretended not to use a CPU while it used a whole core. If the linux app just had said (1 CPU + 1 GPU) instead of (0.15 CPU + 1 GPU) everything would have been fine. That would probably have been something totally easy for any first year student programmer to implement.

Instead you chose to implement something different to utilize less CPU, and with that made next to no use of the GPU along the way. For not-high-end cards it now impossible to crunch a WU in the desired time frame of 24h even for 24/7-crunchers like me, a task that was no problem with the old app.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

The amount of CPU is fixed by the scheduler so it's the same for windows and linux. We would be pretty happy to use 1 CPU for each run and maximum speed, but then others will not like it. That's why we decided to give the opportunity to choose.

gdf

The amount of CPU is fixed by the scheduler so it's the same for windows and linux

How comes other projects have CPU-only and GPU/CPU WUs in stock? As you don't even have any validation process on the single WU, so no chance that Windows and Linux-puters will run the same WU, there should be absolutely no problem to differentiate here.

That's why we decided to give the opportunity to choose.

If there was anything to choose....

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Sänger wrote:

If there was anything to choose....

You have the choice to run the old application (still available) with an app_info.xml file as discussed in another thread.

I'm still running Windows old 6.05 version with 43.478 ms per step on an old GT240 (bought this spring) ;)

77-KASHIF_HIVPR_n1_unbound_so_ba1-70-100-RND5835_0 2103684 23 Nov 2010 17:12:36 UTC 24 Nov 2010 5:29:12 UTC Completed and validated 43,490.56 5,742.65 6,322.41 9,483.62 Anonymous platform

The old application will currently fail on several Ignasi tasks and on all the Gianni. So don't.

gdf

6.12 is also just about as fast as 6.05:

http://www.gpugrid.net/result.php?resultid=3336470
48.331 ms for a GT240 at 1.60GHz.

43.478 ms for a GT240 at 1.76GHz.
http://www.gpugrid.net/result.php?resultid=3341116

48.331/43.478=1.1, but 1.76/1.60=1.1

Both Vista systems with similar CPUs, both KASHIF_HIVPR tasks.

skgiven wrote:

6.12 is also just about as fast as 6.05 ...

You are comparing apples and oranges. The tasks are not similar. Only the time per step looks equal.

Your example tasks:

6.12:
Run time 52299.189003
CPU time 3931.506
Credits 9025.06

6.05:
Run time 43490.557104
CPU time 5742.646
Credits 9483.62

The runtime is on 6.12 ~20% longer and the credits are lower. The cpu usage is ~30% lower.

Btw: I was able to save a task from a acemd2-crash by ignoring the MS message and rebooting: http://www.gpugrid.net/result.php?resultid=3346345
It looks like I've to degrade my NVIDIA driver from 260.99 to 197.45 again.

Ok, so now I've tried adding export SWAN_SYNC=0 to .profile

I've also changed BOINC_USER from boinc to root, & added SWAN_SYNC=0 to /etc/environment

When running boinc-client in root, I've typed echo $SWAN_SYNC & the answer is 0

So WTF is wrong now? 71711

I even had to cancel tasks on 62706 & 70922 because they weren't getting anywhere anytime soon.

---

So WTF is wrong now? 71711

Nothing new, just what I complained about for weeks ;)
Just abort all Kashifs asap, they will not run in time on any Linux machine worth less than a few thousand quid.
Other ones will perhaps make it within the 2-day deadline, but probably no one will be back @project within the desired 1-day time frame.

The project doesn't care about Linux crunchers with ordinary cards inside.

Rubbish apps, every day new and contradicting hints what to do, (upgrade drivers, downgrade drivers, swan-sync whatever, nothing but worthless drivel why and where to put what)

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

They say all Davids are good, but not all Goliaths are bad. But it's things like these which makes all Davids eventually take up a sling & try to take out every Goliath he sees. Wouldn't Goliath rather have a woman take him out instead? Robbing Hood was a thief, but The Sheriff started!

I know it's all about the money, but good will goes both ways, & so does bad will. So do they want people to work for peanuts, or is it dog eat dog, in a world created for Humans?

What started out as mini golf, is starting to look an awful lot like a golf club. People still pay to play mini golf, but only rich people can afford to be a member of a golf club.

I thought everyone was busy smoking cigars in Dubai, so why are they turning mini golf into golf? Don't they have towers to build, formula 1 races to win, football teams to take over, & other vanity projects to pass their time with?

---

You are comparing apples and oranges. The tasks are not similar. Only the time per step looks equal.

OK, here is another more apple like task,
http://www.gpugrid.net/result.php?resultid=3287765

It ran on a card at 1.34GHz, while your task ran at 1.76GHz - your card is clocked 31% faster. My task took 29% longer to run. Same credits.

I also got several MS acemd2-crash Errors - I left the error messages open, closed Boinc, rebooted and the tasks recovered.

The 260.99 NVIDIA driver caused me serious problems on Vista, the clock speeds dropped to their lowest level and it would not let me set them higher, even using EVGA Precision did not force them to stay high. These are Very BAD drivers for many if not most 200 series cards.

The situation appears to be the same on Linux - I have looked at several peoples 6.13 tasks and they are too slow. I'm now trying Ubuntu 10.10, but only installed it last night. CPU tasks run fine, but getting the GPU right is a pain. When I tell NVidia X server (power Mizer) "Prefer maximum performance" it is not saved; on restart it is back to adaptive.
I think the recommended Boinc installation may not be the way forward for GPU users (Applications, Ubuntu Software Centre, search for Boinc) and the default driver appears to be the equivalent to 260.99, at least in terms of being slow and not having controls that work. I have Boinc loading automatically, but even after delaying it's start it appears to be running in power saver mode. 10.10 is different from earlier versions and I'm no Linux expert either. Even swan_sync=0 does not seem to stick, but as I say its another learning curve. I did manage to use swan_sync with Kubuntu 10.04, but I was running the 6.12app and using a reasonable driver. On Ubuntu 10.10 I had to use sudo nautilus /etc/boinc-client to be able to edit the cc_config.xml file, without it I had no access to the file or folder. A bit too much unwanted security all round :(