BOINC@AUSTRALIA FORUM

Active BOINC projects => DRUGDISCOVERY@HOME => Topic started by: Tixx on May 07, 2009, 09:30:47 AM



Title: Re: Project Update
Post by: Tixx on May 07, 2009, 09:30:47 AM
speaking of worthwhile projects, this one looks very interesting.

http://drugdiscoveryathome.com/

not sure if its new, but i cant find links to it either here on the forum, or on the boincstats site..

can anyone shed more light on this project? is it new, abandoned, reliable work, etc??

if its good, ive found my next project to mini-aa on :)


Title: Re: Project Update
Post by: kashi on May 07, 2009, 06:50:04 PM
The DrugDiscovery@Home project developer is Jack Schulz, who is also involved in Hydrogen@Home. It is a BOINC project and the BOINC@AUSTRALIA team was created by Dingo on 21 April. It is an alpha project and so is not likely to run without some problems. It is not currently accepting new accounts without an invite code, so it is not listed on boincstats but is listed on Free-DC.

If you wish to volunteer as an alpha tester before it is publicly available you would need to ask Dingo to ask for an invite code:
"We could use some more hosts. Team leaders, can you contact me for invite codes?" Jack Schulz 6/5/09


Title: Re: Project Update
Post by: Dingo on May 08, 2009, 01:57:27 AM
When a new project is created, our Team and my account are created.  When this project was created I could not log into it and therefor I forgot about it.   I get at least one email to say there is a new project every other month, sometimes more.

I have created the Board for the project and I will have a look when I get home from work today.


Title: Re: Project Update
Post by: Dingo on May 08, 2009, 06:31:53 AM
I have sorted out my account and attached one PC.  I noticed that one of the files was over 20 Mb when it downloaded the first work. 

I have asked for an invite code and I will put it in Members Only when I get it.  REMEMBER that this is still in the Alpha stage and there are still errors in the work units.

http://boinc.drugdiscoveryathome.com/



Title: Re: Project Update
Post by: Dingo on May 08, 2009, 06:39:06 AM


Quote

DD@H is now available on BOINStats and available through BAM!. Mundayweb will follow when Neil is back from his business trip. BOINC Synergy is still down, but I'll email Zain about having us added to their stats anyway.
Ageless
Forum moderator
Volunteer tester



Title: Re: Project Update
Post by: teemac on May 09, 2009, 08:57:50 PM
DrugDiscovery@Home just added to BoincStats today, so are now shown on the TeamStats chart I do nightly.

http://forum.boinc-australia.net/index.php?topic=11.msg25#msg25


Title: Re: Project Update
Post by: Daniel on June 05, 2016, 11:15:53 PM
Someone is trying to revive this project.

They've posted some info on the BOINC message boards ...
https://boinc.berkeley.edu/dev/forum_thread.php?id=11043 (https://boinc.berkeley.edu/dev/forum_thread.php?id=11043)

I hope they're successful. We'll have to wait and see.


Title: Re: Project Update
Post by: Daniel on January 19, 2017, 06:28:25 PM
This project is running again.
It is issuing workunits again and is listed as an active project on BOINC Stats.
I've just joined our team and crunched my first workunit.


Title: Re: Project Update
Post by: Dataman on January 19, 2017, 10:55:19 PM
This project is running again.
It is issuing workunits again and is listed as an active project on BOINC Stats.
I've just joined our team and crunched my first workunit.
Thanks for the info Daniel.  :thumbsup:


Title: Re: Project Update
Post by: Dingo on January 20, 2017, 06:06:07 AM
Thanks Daniel  :fingers that it works.  I have moved the board back to the active list.

EDIT:  Updated the page info and I have completed hundreds of tasks as they only run for a couple of minutes.  


Title: Re: Project Update
Post by: Sean on January 20, 2017, 06:55:15 PM
Thanks, I just re-joined the project...    :thumbsup:


Interesting science too:
https://boinc.drugdiscoveryathome.com/forum_thread.php?id=2050#4601


Title: Re: Project Update
Post by: MAGPIE on January 21, 2017, 10:15:39 AM
Good one Daniel....I have joined also to give it a go  :thanks1:

Looks like a worthwhile cause as well

Really like that a cuda app is coming very soon also


Title: Re: Project Update
Post by: JugNut on February 17, 2017, 07:19:53 PM
Drug Discoveries now has badges..   :thumbsup:

And as mentioned has plans for GPU app  :thumbsup:

And is going to pay users to crunch there.  What the hey now???

The amount is yet undisclosed but they intend to pay users in Ethereum. Ethereum is an atltcoin similar to bitcoin and like bitcoin can be turned into hard cash.  If this is of interest all you need is a digital wallet.  https://boinc.drugdiscoveryathome.com/forum_thread.php?id=2081 (https://boinc.drugdiscoveryathome.com/forum_thread.php?id=2081)

The Admin suggests a digital wallet called "Ethereum wallet"
https://ethereum.org/ (https://ethereum.org/)

These are instructions the admin wrote on a Polish boinc team site.  Site is in Polish but easy to translate within your browser. http://www.boincatpoland.org/ethereum-drugdiscovery-poradnik/ (http://www.boincatpoland.org/ethereum-drugdiscovery-poradnik/)

Interesting concept that the admin says will be implemented very soon. There's already a section to put in your wallet details and they will give you test tokens until they have the bugs worked out. 

Maybe it's just the cynic in me but I wonder why? I mean the site is constantly running out of work so it seems there was no lack of crunching power to be had and that was for free.  Why all of a sudden does he decide to pay crunchers?
I hope it all works out as there's many crunchers could sorely do with some extra cash with the price of power being what it is.
Time will tell I guess?

Any thoughts?


Title: Re: Project Update
Post by: tazzduke on February 17, 2017, 08:07:47 PM
Who knows, I am sure there will be some testers who will give it a go lol.

On another note, I think cause the workunits are shorter, there has been a credit adjustment done.

Oh well, last challenge on BOINCSTATS for this Project, everyone was crunching big numbers, now I think they have come back down to earth.

Oh well thats life.

Regards


Title: Re: Project Update
Post by: JugNut on February 17, 2017, 08:59:19 PM
Your right tazzduke I knew there was something I forgot to post about.  Yesterday I had a bit of a whinge on Drug Discovery forums about about the large downgrade in credit but not surprisingly I did not convince him to put it them back up again,  but I tried :(

https://boinc.drugdiscoveryathome.com/forum_thread.php?id=2076&postid=4767#4767 (https://boinc.drugdiscoveryathome.com/forum_thread.php?id=2076&postid=4767#4767)


Title: Re: Project Update
Post by: chooka03 on April 04, 2017, 08:29:27 PM
Oh dear... looks like Drug Discovery has come to an abrupt end?

https://boinc.drugdiscoveryathome.com/forum_thread.php?id=2091#4830

"Due to some fraud made by part of the team, Me and Goofyx decides to cancel our activity on this project and finish all cooperation with rest of the team.
So, apologise to all volunteers but we had lost half year of work here, and I'm afraid than you too :(

Apologise..."

I saw you guys talking about fraud over on Universe@Home... is Krzysztof referring to the same kind of thing?
No more crunching for me. What a waste :(


Title: Re: Project Update
Post by: Sean on April 04, 2017, 08:36:32 PM
Yeah I was just about to post this, quite alarming...    :shock   :thumbdown:


Title: Re: Project Update
Post by: chooka03 on April 04, 2017, 08:41:10 PM
Suppose I should be changing all my passwords? lol (probably not that funny)  :compbash:


Title: Re: Project Update
Post by: Sean on April 04, 2017, 09:13:26 PM
Suppose I should be changing all my passwords? lol (probably not that funny)  :compbash:

Yeah hard to know the context meant by 'fraud', it could be that the results were used or copied without permission of the team etc...  but that's just speculation...

I removed the project to be on the safe side.


Title: Re: Project Update
Post by: Dataman on April 05, 2017, 12:20:38 AM
That certainly is bad news. I never did much on this project but have removed all traces of it. Removed Acoustics too. Suspended Universe and will keep my eye on it.
Thanks for posting this Chooka. +1
 :bloodshot


Title: Re: Project Update
Post by: JugNut on April 05, 2017, 02:24:18 AM
Wow you have to be kidding me? I put a fair bit of time into this one and was intending to do fair wack more too.  :thumbdown:

Krzysztof has certainly not had a good time of it lately,  first universe falls apart now this.  You have to feel for the guy. Do I think they are both related?  Well anything's possible but it seems highly unlikely. 

Not to worry Chooka there are plenty of bad people in the world so it's not so surprising to find one of them trying to use boinc as a way to scam money.  You've done plenty of good work up to now and your hearts in the right place and I think that's all that counts.  Please don't let one bad experience sour you on the whole boinc experience.  The team would not be the same without you.




 


Title: Re: Project Update
Post by: Dataman on April 05, 2017, 02:35:44 AM
I took a look at the BOINC site and there was no mention of this so I posted a note. Will be interesting what they say.
I didn't take Chooka's post to mean all crunching just DD@H. Otherwise I will have to come over and kick his butt!  :rofl: :rofl: :rofl:
Strange times we live in ...
 :oz:


Title: Re: Project Update
Post by: kashi on April 05, 2017, 04:44:52 AM
This is disappointing, still, it's not the end of the world, there's been bad projects in the past and will be again in the future.

Ironically I crunched some DrugDiscovery@Home in 2009 under it's original developer/admins and they crashed the database and thus deleted my BOINC credit. It was only a small amount so never asked them to attempt to restore it, but never crunched there again until its more recent incarnation.
 
So this is to do with that Ethereum wallet funny business announced a few months ago at Drug Discovery@Home? Thought that was a bit weird. Which also relates to SONM (Supercomputing Organized by Network Mining)? Don't know if payments to Digital BioPharm Ltd were mentioned before. What a tangled web.

Just found something about SONM here, started reading it and my eyes glazed over. Maybe some here will understand it better, the little I read sounded like marketing BS to me:

https://bitcointalk.org/index.php?topic=1845114.0

Finally fitted new memory to Skylake, which has worked without error so far. Finished some Acoustics and now 60% completed 4 instances of PRPNet without a single stop error. Runs at rated XMP 2,666 MHz speed but won't run at rated XMP tight timings, so for now I've given up mucking about with it. Skylake platform compatibility/stability with XMP memory settings at anything over basic 2,133 MHz is just a disaster for so many. Could have saved a bit by buying lower spec RAM but at least this works at rated speed so it's still a win. Will probably light up Gekkos tomorrow, be fun to get gigantor BU credit rolling in again.


Title: Re: Project Update
Post by: Dataman on April 05, 2017, 05:32:08 AM
Well now there is a big "pissing match" going on in the forum between the two sides. Ego's Collide.  :wink

"THIS IS OFFICIAL STATEMENT FROM ANDREY VORONKOV, Lead of DrugDiscovery@home project and former lead of SONM project.

Dear Community members, project SONM was started by me and Sergey Ponomarev during summer 2016. The initial idea of the project was to build it on BOINC platform and develop P2P BOINC technology. Therefore Krzysztof Piszczek and Krzysztof Faryna were invited to make both DrugDiscovery@home and SONM project. DrugDiscovery@home was supposed to be a prototype for SONM project. However, during interaction of our lead developer Krzysztof Piszczek and SONM CTO Sergey Ponomarev different views on technology have started to arise. Sergey Ponomarev has decided to avoid BOINC usage further. As a CEO I tried to unite the team, rather than identify the issue as soon as possible. That was my mistake. Early stage separation of team into two could be a solution. This has led to current team separation. I am convinced that team of Sergey Ponomarev, Alexey Antonov and other team members (russian part basically) can make a successful ICO and a valuable decentralised general-purpose computing platform SONM. Therefore I have signed an agreement with them, which upgrade our technological map and invite new members in the SONM platform.
Project DrugDiscovery@home exists since 2009. Until now the team of Krzysztof Piszczek and Krzysztof Faryna were the best BOINC administrators team, which was managing the project. However, as a CEO I did a mistake and invited the same team into two different projects, which raised issues with another part of the team in the second project. The second project, where our colleagues from Poland were involved was SONM.
Krzysztof Piszczek and Krzysztof Faryna were mostly involved in DrugDiscovery@home project and therefore are very welcome to proceed with its development. All rights on scripts, related to DrugDiscovery@home project are transferred by Sergey Ponomarev to the project DrugDiscovery@home and its team (Krzysztof Piszczek and Krzysztof Faryna). I am ready and happy to ask Krzysztof Piszczek and Krzysztof Faryna to continue their work on DrugDiscovery@home and ready to transfer to them a leading role in DrugDiscovery@home project instead of me.
All efforts and suggestions from BOINC and Blockchain communities to unite the team and prevent destruction of the projects are welcome!"

 :boom:


Title: Re: Project Update
Post by: chooka03 on April 05, 2017, 08:56:00 AM
Wow you have to be kidding me? I put a fair bit of time into this one and was intending to do fair wack more too.  :thumbdown:

Krzysztof has certainly not had a good time of it lately,  first universe falls apart now this.  You have to feel for the guy. Do I think they are both related?  Well anything's possible but it seems highly unlikely. 

Not to worry Chooka there are plenty of bad people in the world so it's not so surprising to find one of them trying to use boinc as a way to scam money.  You've done plenty of good work up to now and your hearts in the right place and I think that's all that counts.  Please don't let one bad experience sour you on the whole boinc experience.  The team would not be the same without you.

Oh..I'm not going ANYWHERE mate!! No way.
Just a waste of time and electricity. I'll stick to the more reputable projects.

I do like Universe @ Home though. Is there a connection between Krzysztof and U@H?


Title: Re: Project Update
Post by: chooka03 on April 05, 2017, 08:56:56 AM
I took a look at the BOINC site and there was no mention of this so I posted a note. Will be interesting what they say.
I didn't take Chooka's post to mean all crunching just DD@H. Otherwise I will have to come over and kick his butt!  :rofl: :rofl: :rofl:
Strange times we live in ...
 :oz:

LOL  :rofl:
You got it Dataman! :) :wave: Here to stay!


Title: Re: Project Update
Post by: chooka03 on April 05, 2017, 09:03:47 AM
Well now there is a big "pissing match" going on in the forum between the two sides. Ego's Collide.  :wink

"THIS IS OFFICIAL STATEMENT FROM ANDREY VORONKOV, Lead of DrugDiscovery@home project and former lead of SONM project.

Dear Community members, project SONM was started by me and Sergey Ponomarev during summer 2016. The initial idea of the project was to build it on BOINC platform and develop P2P BOINC technology. Therefore Krzysztof Piszczek and Krzysztof Faryna were invited to make both DrugDiscovery@home and SONM project. DrugDiscovery@home was supposed to be a prototype for SONM project. However, during interaction of our lead developer Krzysztof Piszczek and SONM CTO Sergey Ponomarev different views on technology have started to arise. Sergey Ponomarev has decided to avoid BOINC usage further. As a CEO I tried to unite the team, rather than identify the issue as soon as possible. That was my mistake. Early stage separation of team into two could be a solution. This has led to current team separation. I am convinced that team of Sergey Ponomarev, Alexey Antonov and other team members (russian part basically) can make a successful ICO and a valuable decentralised general-purpose computing platform SONM. Therefore I have signed an agreement with them, which upgrade our technological map and invite new members in the SONM platform.
Project DrugDiscovery@home exists since 2009. Until now the team of Krzysztof Piszczek and Krzysztof Faryna were the best BOINC administrators team, which was managing the project. However, as a CEO I did a mistake and invited the same team into two different projects, which raised issues with another part of the team in the second project. The second project, where our colleagues from Poland were involved was SONM.
Krzysztof Piszczek and Krzysztof Faryna were mostly involved in DrugDiscovery@home project and therefore are very welcome to proceed with its development. All rights on scripts, related to DrugDiscovery@home project are transferred by Sergey Ponomarev to the project DrugDiscovery@home and its team (Krzysztof Piszczek and Krzysztof Faryna). I am ready and happy to ask Krzysztof Piszczek and Krzysztof Faryna to continue their work on DrugDiscovery@home and ready to transfer to them a leading role in DrugDiscovery@home project instead of me.
All efforts and suggestions from BOINC and Blockchain communities to unite the team and prevent destruction of the projects are welcome!"

 :boom:

Hmm....made no sense at all to me.
I have realised I need to do more research on the projects I choose to crunch for though. As mentioned before, due to my Ukrainian roots, I'm distrustful of anything Russian and won't support anything Russian.
If DD@H is Russian based, I'm out. I'f it's Polish...well that's ok.

Sounds a bit ..... Xenophobic.... but you know what...that's my prerogative. There are HEAPS more projects to spend time & money (electricity) on.

Edit - I see  Krzysztof is from the University of Warsaw. I'm cool with that....... :thumbsup:.... unless he's a Ruski spy  :bloodshot lol


Title: Re: Project Update
Post by: Dingo on April 05, 2017, 09:49:58 AM
I have stopped members from joining the Team and sent out an email to Team members on that project with the links the forums.

Will wait an see what happens.


Title: Re: Project Update
Post by: chooka03 on April 05, 2017, 06:52:08 PM
Quick question? Ho do I get rid of all the aborted WU's no clogging up my BOINC manager?


Title: Re: Project Update
Post by: kashi on April 05, 2017, 08:00:14 PM
I'm not attached to project, so don't know if server is turned off. Have you tried "Reset Project", that's normally used to get rid of everything in the project directory.


Title: Re: Project Update
Post by: Dataman on April 06, 2017, 01:09:14 AM
I took a look at the BOINC site and there was no mention of this so I posted a note. Will be interesting what they say.
I didn't take Chooka's post to mean all crunching just DD@H. Otherwise I will have to come over and kick his butt!  :rofl: :rofl: :rofl:
Strange times we live in ...
 :oz:

LOL  :rofl:
You got it Dataman! :) :wave: Here to stay!
Good! That saved me a long plane trip wearing my pointy toe cowboy boots.  :rofl:
I thought doing "Remove Project" would get rid of any wu's too but cannot remember ever trying it. You can of course uninstall BOINC and reinstall it. Just looked and only the web server and scheduler are running.
 :greet


Title: Re: Project Update
Post by: Sean on April 06, 2017, 08:26:11 AM
Yeah I think 'Remove Project' should get rid of them like Dataman said, otherwise they'll be stored in a folder under 'C:\ProgramData\BOINC\projects'    :thumbsup:


Title: Re: Project Update
Post by: chooka03 on April 06, 2017, 06:57:54 PM
Does removing the project also remove a trace of my involvement? ie - lose all my credit points and badge?
I'd rather not lose those even if the project is dead. :fingers

Edit - Doesn't matter, I removed it anyway.
The pages of aborted WU's weren't going to disappear on their own and were very annoying. Problem now solved


Title: Re: Project Update
Post by: JugNut on April 06, 2017, 11:33:23 PM
Yea there safe chooka.  Even if a project shuts down your credits are kept with the external stats sites like boinc stats, free-DC &  signature stat sites like boinc.mundayweb.com plus others. The same with badges at https://signature.statseb.fr/.  Free-DC keeps track of badges too. 
So long story short as long as there's external stats sites it's all good ;)

I guess that's a good reason to support their funding campaigns either directly or at Bitcoin Utopia.  Boinc wouldn't be the same without them.

Crunch-on  :crazy 


Title: Re: Project Update
Post by: chooka03 on April 07, 2017, 08:59:35 PM
Never knew what Free DC did.
Thx  :thumbsup:


Title: Re: Project Update
Post by: chooka03 on October 18, 2017, 04:29:36 PM
CUDA app testing.

Are we about to see an explosion of credit points with this project for people with NVIDIA cards? Looks like it.

https://boinc.drugdiscoveryathome.com



Title: Re: Project Update
Post by: tazzduke on October 18, 2017, 08:42:59 PM
Greetings All

It does have some special requirements, which is explained via the link that chooka03 has posted.

Out of my 4 crunchers, only 1 can do it and thats the AMD Ryzen 1400 due to it having the required AVX2 cpu component.

The others are Core2Quad crunchers.


Title: Re: Project Update
Post by: kashi on October 18, 2017, 09:52:17 PM
Seems like it's missing a very basic "special requirement" to work on my Skylake computer also. "No tasks are available for gromacs."

Forget if this project uses CreditNew or not, for CPU it is known to be an unreliable and inconsistent system, but using it for GPU tasks can result in very extreme swings in credit rate.

I'll give it a go if there are any more tasks issued.
Thanks for the alert Chooka.


Title: Re: Project Update
Post by: JugNut on October 19, 2017, 10:25:17 AM
These WU's don't require AVX2 but as I found out they do need AVX in order to run.  The WU's themselves are extremely poor on GPU utilisation, on my bigger cards 1 WU's uses just 7% - 8% of the GPU load.  In fact even when running multiple(up to five) using an app_config I couldn't get past 75% load. But unlike all other GPU apps i've ever used running multiple instances at once doesn't increase the runtime of any single one of them.  Stranger still even at only 75% load most of my cards heat up just like they were under full load,  the same as running 2 of einsteins GPU WU's in parallel would do.

While the credits are OK i'm still not a fan of these as yet as there just seems to be to many unknown questions about how and why they run the way they do.
Also i'm pretty sure the GPU WU's are not using credit new but still credits are all over the place.  When I first looked at what others were getting I thought wow that's alright 250k-450k per 6 - 8hr work unit but the longest WU i've run so far gave 72,208 credit. But even then I have  quite a few other WU's that ran very similar times but only gave 25,000 credit. It seems to be a lucky dip,  if you're lucky you could clean big time.  If not then you "should" still do OK.  Although it seems at least possible to do poorly. In other words things have a looong way before they settle down.  I may finish up the WU's I have then come back an try again at a latter date.

But I suppose thats the price you pay for alpha testing a new GPU app.

For any one interested this is my working app_config that I am now using on a box with 2 x GTX 970,s.  As I need as many free CPU cores as possible for WCG i'm only running 3 WU's in parallel in the app_config listed below(0.33). Just change the numbers as per your needs.
You can remove the vina part of the app_config if you don't need control over the vina CPU app.

<app_config>

<app>
<name>gmx</name>
<gpu_versions>
<gpu_usage>0.33</gpu_usage>
<cpu_usage>0.5</cpu_usage>
<max_concurrent>6</max_concurrent>
</gpu_versions>
</app>

<app>
<name>vina</name>
<max_concurrent>10</max_concurrent>
</app>

</app_config>


Title: Re: Project Update
Post by: kashi on October 19, 2017, 11:32:21 AM
I'm doing 2 concurrent on my GTX 970, GPU load is fluctuating between 60% to 72%. The 2 I completed so far paid quite poorly for GPU tasks, one ran 4.7 hours for 16,448 credits, the other 5 hours for 17,400 credits. No 500,000 and higher credit tasks for me, like some others are getting.
 
Can't think of a reason credit is so erratic unless CreditNew is being used. Unless perhaps the admin is mucking around changing the credit rate with little idea of what he's doing.

A resend with a shorter deadline caused 1 task that was almost finished to stop processing at 85% complete, grrr. When I paused that resend the original task started again from the start. Checkpoints aren't working on my computer even if the admin says they are.

So yes, quite flaky at present, some of the old resends that I let run for a while were showing that they would take over 30 hours to complete. So I aborted those ones. Think I'll give it a miss too after these 2 current tasks complete. They're going to run about 9 hours. If I'm going to risk doing GPU tasks that long I'd prefer more reliable GPUGrid tasks, plus I'd get a more generous and consistent credit rate there as well.


Title: Re: Project Update
Post by: JugNut on October 19, 2017, 12:24:23 PM
I'm doing 2 concurrent on my GTX 970, GPU load......

A resend with a shorter deadline caused 1 task that was almost finished to stop processing at 85% complete, grrr.


Yep same happened to me but I was even luckier and was at 99.325%.  When I noticed what had happened I tried suspending the interloper & allowing the the old WU at 99.3% to run again, but then I seen the same thing as you did.  The old WU that was at 99% had restarted from scratch, so then aborted both them.  It was only then did I read that they are supposed to checkpoint in some "other" non-boinc way. But of course by then it was way to late to test out that theory.  But I did check the stderr file before I aborted it & it said there were zero checkpoints.  So in the end i'm buggered if I know? 

It seems strange things be afoot tonight hey Watson?  Sheesh! Where's Holmes when you really need him?  :wink


Title: Re: Project Update
Post by: kashi on October 19, 2017, 12:49:39 PM
Yes, I looked at the stderr.txt file in the slots folder, the Gromacs application itself seemed to set a backup checkpoint*, but as far as I could tell the GPU wrapper didn't use it and the task started again from the beginning.

* Stderr.txt said something like: "Back Off! I just backed up md.log to ./#md.log.2#"

My last 2 tasks that were heading for 9 hours just completed at about 5 hours, so the Remaining (estimated) in BOINC Manager is of little use. Similar low credit to my first 2 completed.

Server out of tasks again, I'll leave it requesting work and have one more try to snag a credit whopper but looks like they're finished now.


Title: Re: Project Update
Post by: chooka03 on October 19, 2017, 05:19:43 PM
Been reading a bit lately about Kaspersky..... maybe these guys work for the FSB looking to use network computing to do their dirty work?  :thumbdown:

{Did I just say that!!}  :holy-moly

http://www.skynews.com.au/news/world/nthamerica/2017/10/12/israel-warned-us-of-russia-s-kaspersky-hack.html


Title: Re: Project Update
Post by: JugNut on October 21, 2017, 01:34:59 AM
Just finished some version 0.24 WU's that are giving a lot better credit. LINK (https://boinc.drugdiscoveryathome.com/results.php?hostid=1900&offset=0&show_names=0&state=4&appid=)

I just noticed there is now an even later version 0.25. I'm crossing my fingers that this time they've finally got their credit system sorted and it stays as it is now?  But until I finish some I can't say.  As mentioned you can run 3, 4, 5 or more at time so if credit stays the way it is now it will indeed be a well crediting project. 
For anyone interested in giving them a try there is now plenty of work available.  For how long is anyone's guess?

Crunch-on :crazy

EDIT version 0.26 just released,  apparently checkpoints are now showing in boinc & the progress bar is now more accurate.(well it updates progress every 15mins at least)  I have quite a big queue of the other versions so it will be a fair a while until I get to test any of these.  If you crunch any let us know how they go. 

Oh, and what credit they gave too.  LOL can't forget that.

 


Title: Re: Project Update
Post by: kashi on October 21, 2017, 02:44:22 AM
And now there's version 0.26, with checkpoints supposedly working.

Hmm, those tasty v0.24 ones you completed were all old resends originally issued on the 17th. In the past, those were the ones that could sometimes give the more generous credit.

Although I snagged a single v0.24 that was a fresh resend that credited 95,906 for a 2.75 hour runtime. So that's much better than any of my previous tasks. Was using nt 3 parameter too, didn't seem to increase GPU load percentage at all but made the Afterburner graph of it much flatter and less sawtoothed.

Currently my 970 is working on 2 concurrent v0.25 tasks. They're now at about 50% complete after 2 hours, so should finish just before "breakfast". So then we'll see what they grant and if credit system is still wildly inconsistent. Be nice if it stayed generous at least for a while as nt 3 uses up my CPU cores, so WCG badge hunting is slowed a bit.

Aha, you've updated your post while I was writing this post.

Edit: And I just increased my cache and both tasks swapped out and went into Waiting to run state. Each with 2.5 hours runtime and 61% completion lost. Bah!


Title: Re: Project Update
Post by: JugNut on October 21, 2017, 07:11:43 AM
Not to worry kashi at least now you get to test out the checkpointing ;)



EDIT: Mmm I Spoke to soon it looks i'll soon get that opportunity as well.  You really have to keep your eye out for those short deadlined resends.  Now if I see one that hasn't yet jumped to lightspeed I abort it straight away.

Oh and what about those uploads & download?  There huge!!  With all the ancillary files the uploads get up around the 36 - 39MB each and downloads aren't far off it either. Lucky most are long runners or it would be a big hit to those without unlimited internet plans.



Title: Re: Project Update
Post by: kashi on October 21, 2017, 08:08:30 AM
Haha, yes resume from checkpoint still not working in v0.25, that's why I exclaimed "Bah!". Have set No new tasks and reduced cache setting to hopefully avoid further annoying swap outs. Haven't tried checkpointing on v 0.26, still have oodles of v0.25 left, the first 2  I completed paid exactly the same credit rate as the v0.24 I completed.

Credit scales exactly with runtime for the last 3 tasks completed, so I've reverted to nt 1 from nt 3 and now doing 4 concurrent nt 1 rather than X2 nt 3. Tasks take more than twice as long without nt 3, so X4 nt 1 probably about 10% less efficient, but total credit yield should more than double due to runtime scaling.

GPU load is flicking between 68% and 76%, could possibly go 5 concurrent for a little extra but 4 will hopefully do nicely enough. If credit rate scaling remains the same as last 3 tasks, daily total will be huge at 4 concurrent.  v:


Title: Re: Project Update
Post by: JugNut on October 21, 2017, 10:03:31 AM
Yep thats what I ended up with 4 x concurrent on most my cards except for a single 980 ti that i'm testing 5 at a time on.  If I had 2 980's that would be 10 cores i'd have to keep free.  I'm thinking about stopping CPU work altogether as these guys seem to like as much CPU time as possible. At the moment nt1 is working out nicely so i'm leaving it as is for now.

Also i've noticed on the 5960x the CPU is at maximum power draw something i've never seen before. For some reason they are giving my PC's a good workout as the fans on my boxes are screaming like an army of angry banshee's.



EDIT: Jeeper's!!! If you thought those last WU's credited well then have a look at these... Link.. (https://boinc.drugdiscoveryathome.com/results.php?hostid=1903&offset=0&show_names=0&state=4&appid=)

At this rate i'll have a billion credit before the days out.  :rofl: 
Ok that's a slight exaggeration on my part, but boy they are crediting well to say the least.


EDIT2: With the extra push of that last batch of big crediting jobs I jumped into fourth place...   :dance: 

Sing it loud..... happy days are here again the skies above are clear again,  let us sing a song of cheer again,  happy days are here again da da da da da dar....(it's an old war song my dad used to sing all the time) Song Link... (https://www.youtube.com/watch?v=Gt2Rmx-h84I0)

EDIT3: Going up...  now in 3rd place..


Title: Re: Project Update
Post by: kashi on October 21, 2017, 01:47:47 PM
Yep, you've really hit the jackpot on that machine.  :cheer1:

It's gotta be some form of CreditNew hasn't it, surely nothing else is that wildly, erraticly, inconsistent as to give hugely different credit rates to different computers with similar hardware specs for the same batch of tasks. Don't even need one of the fastest cards either, Tazzduke had a 622K task on his GTX 960 a few days ago.

My last 4 tasks completed and credited at the same hourly rate as the 3 before them. So if I multiply that by 4 concurrent, then by 24 hours, it should yield around 3.3 million, woohoo.

Know that song very well, my mum used to sing it sometimes, she sang it in a concert at Sydney Girls' High about 1941, which she won. Don't remember hearing that version you posted before, can remember a female version from when I was young, probably Patti Page. Then later on one by Max Bygraves. Slow version was Barbra Streisand's "signature song" during the early part of her career and was on her first LP.

Yeh, it's fun roaring up the charts, ain't it. I've zoomed up 130 places in the last 3 days, haha. v:

Edit: Ah, didn't notice, statseb just informed me of new badge. Oooh, giant, blue and shiny. :crazy


Title: Re: Project Update
Post by: tazzduke on October 21, 2017, 05:54:14 PM
Greetings All

Yeah, I did strike it lucky with that one, but the others not so, now I just cant seem to get anything, so I have left it open to see if I can snag a task or two.  I just want to get to 1 million anyways.

I would be one of many who cannot participate if I didnt do my long overdue rebuild.

But I am kicking myself for not getting the 17y00 instead of the 1400, I could have had 16 cores instead of 8 cores.  Oh well, bit late now.

Well anyways, I am still crunching WCG for the time being.


Title: Re: Project Update
Post by: kashi on October 21, 2017, 06:45:00 PM
Yeh, I couldn't get any for a day or so too. Well, did get 1. Then got heaps. Will abort those later that will not finish before deadline, that will release some for others. Just testing some v0.26 tasks first to see if they credit the same as v0.25.

Probably only a few people have any tasks, and those that do would have tried to maximise their cache in case future tasks grant less. It's unfair really but happens commonly with limited batches of tasks available when new projects are under development.

Wouldn't matter if credit rate was consistent, anyone could easily catch up later. But if credit rate drops later then those who got lots of early credit monsters are unable to be overtaken easily or at all. With limited task availability, admin should have put a limit on number of tasks per GPU allowed in cache but he's been busy trying to get checkpoints working instead, plus faffing around with Linux compile questions.

Yep, I've still got both E5-2670 CPUs fully on WCG. Finished up with MCM for now and concentrating on next FA@H2 and HS TB badges.


Title: Re: Project Update
Post by: tazzduke on October 21, 2017, 07:59:25 PM
Hey I got one lol



Title: Re: Project Update
Post by: JugNut on October 22, 2017, 01:44:02 AM
Now i'm not opposed to a good a days credit but yesterday I received over 20mil for just that one day,  even for me thats a tad excessive.    That kind of credit is unsustainable, I mean the only other project where I could get a similar total would be at Collatz and only then by heavily tuning the app.  But the Collatz project uses a tiny math app that's been worked on and optimised year after year by a skilled programmer so in some ways I can understand why they give the credit they do,  but that's not the case for Drug Discovery in fact their app is the total opposite.

The thing is at around the 250k mark for a 7 or 8 hour work unit that would have been quite acceptable and is somewhere around what GPUgrid gives in credit but because the Drug Discoveries app is so inefficient and you can run 3, 4 or more instances at once which of course means you  receive 3, 4 or more times the credit than you normally would do too.

Normally I despise people who complain about getting good credit thereby ruining everyones elses fun when its eventually changed thats why I wont be mentioning it on Drug Discoveries website,  but I still think it needs changing as it is more than just a tad extreme. Regardless of what I think it usually not long before a kill joy or two does start complaining and that may be the end of that.  So if you're looking for a quick top up on credit well nows the time as it might not be there in the future.   

But all in all it's great to have another Bio project that uses GPU's.

What do you guys think? To much? Or do you think there should be no limits on credit at all?

Anyway for now let the credit flow & the drugs be discovered.. LOL 

Crunch-on..


Title: Re: Project Update
Post by: kashi on October 22, 2017, 04:46:53 AM
Well high credit in itself is not a problem so much if it is a consistent rate, there are sufficient tasks available for all and application is reasonably efficient and not overly CPU bound.

Then many people get the chance to enjoy a project with high credit and the project itself may interest them as well. I certainly enjoy a project more when credit rate is high rather than stingy. Although credit's not the only criterion for choice, rather employ my GPU on GPUGrid or DrugDiscovery than on Collatz, regardless of credit rate.

However when the rate repeatedly varies excessively from lowish to very high, depending on when you downloaded a batch then it is unfair.

When documentation is poor and doesn't mention that a recent GPU driver version is required that is also unfair.

Most importantly when available tasks are limited and no restriction is placed on cache size, that is the unkindest cut of all. It means some like me and you can gallop up the charts with our fat caches whilst others suffer a task drought and are unable to join in the credit party.

There's a few problems causing this and they've happened a number of times before.

Firstly, the use of a credit system that varies the amount of credit granted proportionally according to runtime. This on a GPU project that has the second problem is a proven recipe for credit mayhem.

Secondly, as already mentioned, a GPU application that is extremely inefficient and/or CPU bound. This causes the running of multiple concurrent GPU tasks to try and use the GPU more efficiently. Not only does this greatly multiply any very high credit rate batch tasks but it also uses up all your CPU cores so prevents other projects being run.

Thirdly the lack of a cache size limit on a new project with limited tasks available causes a task feast for a few and a task famine for many. Cache limit is easy to implement through the BOINC software and should be done as a priority when task availability is limited.

Admins who are struggling just to get new applications to work without crashing and to checkpoint properly may not have sufficient working knowledge of various BOINC credit systems to avoid the greatly increased potential of runtime based credit systems going totally haywire when used for GPU applications.

Sometimes think they're a bit lacking in GPU application development skills. May be whizzes at compiling Linux applications and other programming, but perhaps have little experience and knowledge of how to optimise GPU CUDA or OpenCL code for a range of modern GPUs. If they can get their GPU applications to work without errors and checkpoint then that's it, job done. Always felt POEM was like that.

Yes good to have another Bio project for GPUs; even though I've currently got an Nvidia myself, still unfortunate it's not AMD GPU too though.

I've copped it many times on different projects when I've missed the boat on getting any early gigantor credit tasks, so other than a slight twinge I'm not going to be embarrassed by roaring up the charts because I managed to snag a cache of big 'uns. Bonanza will probably end soon enough so I'll just enjoy this tasty credit boost while it lasts.


Title: Re: Project Update
Post by: tazzduke on October 22, 2017, 11:00:56 AM
Greetings All

Just got through 3 tasks and well yep credit is all over the place lol.

But then I forgot to apply an app_info file so I could run 2 tasks at a time and just got 9 tasks, so I will have to wait till they go through and then try again.

I am running a GTX 960 though, so am not sure if its even worth while.

Cheers.


Title: Re: Project Update
Post by: chooka03 on October 22, 2017, 02:20:05 PM
Meanwhile those of us with AMD cards just watch on  :thumbdown:

I'm not worried though. Plenty of other things to crunch :)


Title: Re: Project Update
Post by: kashi on October 22, 2017, 02:41:26 PM
Yes, looks like credit is on the way down again. My last task dropped by 81% compared to rate of my recent previous tasks. Never got any of the super dooper 500,000+ credit tasks, just the high 170,000 to 220,000 ones. At that 81% lower rate, daily yield would be similar to GPUGrid, but GPUGrid doesn't use all my CPU cores or make computer run as hot. See what happens with the current 4 tasks in progress, if they're same as last one then I'll sing my song and I'll be gone*.

Be a relief in some ways as I'll be able to add this computer back with other box's WCG badge hunting efforts. Those Sapphire badges and higher take a power of processing even with many cores a crunchin'.

At least our DrugDiscovery million badges are prettier than the blurry 100,000 one. Plus the team is in 2nd place too.

Be good if the application can be optimised in the future to be more efficient and not require hogging all your CPU cores to use your GPU efficiently. I mean you can already optimise it greatly with use of nt parameter but that still uses all your CPU cores.

Maybe wishful thinking, but would be nice to have another GPU Bio project available that was well behaved and stable. Fixed credit and a cache limit of 1 or 2 tasks per GPU, like GPUGrid can fix the credit problems and then another nifty project choice for Nvidia owners is available. Everyone has their preferences but I prefer to use my GPU searching for curative drugs rather than aliens. No AMD GPU support is a continuing unfortunate theme of course, as it restricts GPU purchasing choice, reduces potential project participation and prevents project being AA target.

The pity about not properly taking care of credit considerations with a new project is that once the admins wake up and finally do something about it, they often overreact and go to the stingy dark side. This means that the oodles of credit amassed by the early adopters cannot be easily overtaken which reduces incentive for competitive crunchers in the future. Even when it is necessary and justified, a sudden massive reduction in credit rate always leaves a bad taste, haha. 

*Haha, remember Spectrum:
Someday I'll have money
Money isn't easy come by
By the time it's come by I'll be gone
I'll sing my song and I'll be gone


Title: Re: Project Update
Post by: tazzduke on October 22, 2017, 03:17:03 PM
Afternoon, figured it out with the app_config file, but once these are done am fully back onto WCG.

Yeah I remember Spectrum lol.

Its a motto around here sometimes lol.


Title: Re: Project Update
Post by: tazzduke on October 22, 2017, 09:44:40 PM
Oh my the app_config file is not behaving like it should.

Oh I got me an error on job, oh bother.

Thats is, shutting down the GPU, running all cores on WCG for a few days while the temps are down outside.

I thought I might be able to get a blue badge on of the subprojects but will see about that lol.

Cheers and have a good night.


Title: Re: Project Update
Post by: kashi on October 23, 2017, 12:58:08 AM
Tarnation, how annoying!  :boom:

Just noticed those 9 tasks you downloaded were Gromacs_v2 tasks. That's a new application just released yesterday.  As far as I can see, all Gromacs_v2 tasks completed are failing on upload same as yours with "file_xfer_error" messages. Small consolation I know, but it's not just you.

Have set this GPU equipped box to cleaning up some WCG tasks in my cache for the next 11 hours or so, than may try a few more DrugDiscovery GPU v0.26 tasks. After the credit drop, was fiddling around trying out different nt values with 2 tasks and the last task I completed doubled the credit rate per task again from its lowered rate of 30-40K back to 89K.

Not sure if it's actual CreditNew at work with these large credit fluctuations or the admin repeatedly trying and failing to fix the credit rate so it is reasonable for all. Either way, credit stability and consistency is probably impossible with such an inefficient GPU application. Means this messiness will continue until he either increases the efficiency and/or uses fixed credit.

Just for interest a single task with nt 4 took 102 minutes to complete and a task with nt 6 took 79 minutes. Good thing is the v.026 application now multiplies the actual runtime by the nt value and reports it as elapsed time. Previously actual elapsed time was reported and used for credit calculation, so you were penalised much more heavily then for increased efficiency.

For comparison running 4 concurrent tasks with default nt 1, each task completes in 306 to 387 minutes. Remembering application is heavily CPU bound so GPU load and task runtime varies a fair bit depending on whether spare CPU cores are used for CPU projects or left free. Think I was running 3 WCG tasks with the nt4 task and no CPU tasks with nt 6.  

CPU cores really heat up running a single task nt 4 and nt 6, even with no CPU tasks running. So GPU application is actually heavily using CPU resources and not just that weird Nvidia bug/feature with GPU applications where a CPU core is reported as being used, but actual CPU usage is very low.


Title: Re: Project Update
Post by: JugNut on October 23, 2017, 02:07:19 PM
@tazzduke:  Eeek.. that's terrible ,  at least they seem to have canceled all the rest of them for now.  So far I haven't received any of those so they must be a work in progress.


@kashi:  You know I must be getting slow in my old age. I'm not sure why it didn't dawn on me before but the reason that these tasks run much the same on my gtx 970's as they do on the pair of 1080's is because there totally CPU bound. While we had already come to this conclusion yesterday but what I hadn't taken into account was the effect AVX plays in all this. Since the tasks use AVX and by nature AVX tries to use a full core and gets no advantage from hyper threading that means the box with the pair of 1080's in it should have 8 full cores to feed the 8 GPU tasks, which it does not. 
I should only be running at most 3 tasks concurrently on each GPU. Why? Because that box only has a 6 core 12 thread CPU in it and not only have I been running  4 x GPU tasks concurrently on each GPU i've also been running the extra WCG tasks to boot. That can only mean lots of contention.  In other words there's 8 GPU AVX tasks fighting for 6 cores.  And those cores already have WCG tasks on them which only makes matters even worse. I presume that's why the CPU is working so hard & getting so hot too.
 
As we've talked about before technically the best way to run these GPU AVX apps would be to disable any other CPU based WU's reboot the PC and disable hyperthreading in BIOS then only run the the amount of actual cores you have,  just like any other AVX CPU app would do,  just like you might do with LLR tasks from Prime Grid.
Of course that's a pain and the few times I have ever tried it there wasn't a huge advantage anyway,  but theoretically it should work.

On the other side my gtx 970's have a 8 core 16 thread CPU at their disposal which mean even though the GPU is slower the app can still run close to it's full speed whereas the 1080s can't.(even after disabling WCG work)

I can't say for sure but I doubt credit new is being used with these as credit new seems to be a means to stabilize credit and even reduce it year on year as hardware power increases, so I just find it hard to imagine credit new giving such huge credits at any time.  I'm sure there'd be a way of finding out but I have no idea of how?

Also I think the "nt" switch is not such as good solution as it first sounds because most people still only have limited "actual" cores. So if you run 4 GPU work units you'll need four real cores. So in that scenario setting anything other than nt 1 should not work well at all especially if you use the most common of all CPU's the intel i5 4 core or the i7 4 core 8 threader as both only have 4 real cores. I suppose if you set nt 2 and only used 2 GPU task concurrently that might work out with a 4 core chip?

Of course this is just theoretical and only actual testing with this in mind will find the best sweet spot.

Anyhoo I thought i'd share my epiphany even though now I think of it,  it's quite obvious.

Mmm I wonder how your 970 would go in the Asus server box?  For all intensive purposes you'd have plenty of core's to feed the GPU whatever it needed.  Might be a hassle to implement but wonder just how far you could load it up?  Just a thought...

Crunch-on.... 


PS: 28mil in credit yesterday which rocketed me into first place!!  I've never been this lucky before i'm not sure if I should be elated or embarrassed? I wonder how long it will be before they reverse the over crediting?  Oh well, easy come easy go...



Title: Re: Project Update
Post by: kashi on October 24, 2017, 12:19:58 AM
Congratulations on first place and achieving the 50 million DNA helix badge.  :congrats  :congrats
 
Ah yes, it had occurred to me to run a single task using nt 32 parameter for fun in dual box, if it had a GPU installed. Think it may not work too well though because of how the 2 separate CPUs interact with the memory and other resources. Kind of intra socket contention issues. Sometimes you can partly get around these issues causing slowdown of multithreaded CPU programs by running 2 program instances and allocating program threads/cores to a particular CPU using Task Scheduler or Process Lasso. However for GPU applications I think the lanes on one PCIe slot map to one CPU and another slot maps to other CPU. So you'd perhaps need 2 GPUs to utilise both CPUs.

Didn't think of turning off hyperthreading though, haven't wanted to use all 8 CPU "cores" on Skylake box because it's running warm enough just using 6 (X3 tasks with nt 2). But it may run a fair bit cooler running all 4 cores with hyperthreading off, might try it tomorrow.

However as you said when it comes to GPU applications rather than solely CPU applications, sometimes turning hyperthreading off gives little or no advantage. Plus without the elapsed time multiplier effect of running X4 tasks with nt 2 like you can with hyperthreading on, it may end up being more efficient by completing more tasks per day but actually get less daily credit. That's always irritating when a faulty credit scheme promotes inefficiency.

Gromacs is complaining of the inefficiency of not using -pin on (and -pinoffset for multiple jobs). Could try fixing threads to cores I suppose, haven't used Process Lasso for a while. Just tried 1 task with nt 7 and it completed in 71 minutes, now have cleaned heatsink of CPU a little plus also filters on case and am running 1 task at nt 8. GPU and CPU temps are warmish but acceptable, slightly less than when running 4 concurrent at nt 1. Afterburner GPU usage % graph line is very smooth and steady at 64% to 66%. Task Manager Details tab shows gmx.exe using 92% to 94% of CPU.

Probably will only be a tiny bit faster if at all than nt 7, but runtime will be multiplied by 8 instead of by 7. Think I'll leave it on that overnight as it seems stable. Dual box is crunching away on WCG without complaint.

Actually CreditNew has a history of wild and erratic spiking and dipping when being used with GPU applications. It has no effective mechanism to consistently compensate for the large differences in Runtime when used with inefficient GPU applications and the resulting concurrent type processing. Can't remember which projects, but quite a few had big trouble with CreditNew and had to hurriedly introduce fixed credit. Think that included either DNETC@HOME or Moo! Wrapper (or both!).

Even with CPU applications it can muck up. Aqua@Home had so much recurring strife with the incompatibility of CreditNew with their multithreaded CPU application causing massive credit spikes that they gave up and left BOINC completely. Plus CreditNew has a comparison feature that is supposed to compare with other projects and adjust the credit rate accordingly. When CreditNew was first used on WCG they were alarmed and dismayed that the credit rate was automatically increased to a reasonable rate and hurriedly disabled that feature as they are totally wedded to the unwholesome, inconsistent, illogical, unfair "reduce towards zero" credit philosophy.

So much so, that on WCG a recent architecture CPU will often have a credit rate that's similar or even less than a CPU architecture from years ago, even though efficency of more recent CPU architectures has increased greatly. They hate the whole idea of credit at WCG which is why they invented their colourful Runtime badges to ensure people with old, inefficient "boat anchor" CPUs could pretend they were doing a useful amount of work instead of basically just wasting power.

Gee I'm twitter and bisted sometimes. Never miss an opportunity to bag WCG's "war on credit" stinginess even though I often turn my bedroom into a bath of fire runnning 3 CPUs/35 cores on their projects to help cure diseases.  Anyway, have a few Emeralds pending and will probably go for Zika Sapphire next, seeing as can't get many HS TB tasks at all. Maybe I too need to employ "old batchie" at the 3rd and 33rd minute every hour, haha.



 


Title: Re: Project Update
Post by: JugNut on October 24, 2017, 08:35:17 AM
Hey thanks kashi, 
I suppose it had to happen eventually but my credit output is now down by well over half what is was the day before,  although that hasn't happened across the board though as i've noticed there are now others getting the same credit what I was receiving and are now racing up the ranks behind me.  The funny thing is that one box that received the lions share of the credits performed quite poorly in the first place.
I wish I knew which setting controlled the credit boost though.  It would be awesome if everyone in the team could receive the same huge credits for a time and that way the team could get a massive head start on this project.  But sadly I have no idea what caused the spike as it was probably just a bit of luck. But you can bet your boots I looked into it anyway. LOL

Oh! And i'm sure you're right about credit new kashi but with my inbuilt bias against it I just couldn't imagine it ever giving something good to anyone at any time,  plus had never done either of those projects you mentioned,  so happily or sadly depending on your point of view I missed out on those particular rounds of credit craziness.  Thanks for the info.

Anyway time to prepare for another fun day at the doctors.  Oh well C'est la vie

Crunch em if you got em..  :crazy


Title: Re: Project Update
Post by: kashi on October 24, 2017, 07:32:10 PM
Yes you're quite right, CreditNew as used in CPU projects almost always causes very low credit because it applies the horrid, illogical "reduce towards zero" concept whereby newer faster computers are automatically crippled credit wise and awarded credits within the usual despised stingy range.  

However admins who are uninformed or misguided enough to ignore repeated history and try and use CreditNew for GPU applications may often be the same type who panic when credit rate spikes ridiculously high. Then they may repeatedly manually adjust the task parameters relating to credit calculation to try and restore stability. The CreditNew "smarts" then "fights back" and the yoyo continues.

Wouldn't feel guilty over winning the occasional credit lottery. The oodles of years of processing time we've donated to projects where credit is unjustifiably low and a poor recompense for the many thousands of bucks we've spent on crunching computers, expensive GPUs, power and/or solar installations more than balances it out. You wouldn't have any colourful WCG badges at all if you lived by credit alone. But despite the holier than thou lamentations of the anti-credit whingers, avid Cruncherman does not live by badges alone either, so just enjoy it as a random bonus.

Don't think I got much advantage from those 3 projects I mentioned. Aqua@Home was a lucky dip as only a small number of contributors quickly gobbled up all the task batches where the credit was huge. Remember being a bit disappointed that I missed out. Can't remember for sure but I think they removed/reduced some credit also when it became too excessive. Think one or both of the GPU projects quickly and wisely moved to fixed credits, so again don't remember getting any bonanza there either. Also I was possibly focussing on MilkyWay@Home on GPU back then, so just observing for interest.

Back to DrugDiscovery, yes the team is building up a handy total. Not going to do any more testing of different task number and nt combinations. Getting very warm in this room today and GPU runs cooler running only a single task. Possibly could get more doing multiple concurrent but although rate continues to gradually drop, single task daily yield is currently still "quite generous", mwuhahaha.