rogue project: Test4Theory@home, don't join
log in

Advanced search

Message boards : Cafe : rogue project: Test4Theory@home, don't join

Author Message
jujube
Send message
Joined: 24 Oct 12
Posts: 1
Credit: 0
RAC: 0
Message 356 - Posted: 24 Oct 2012, 2:50:00 UTC

I am a moderator at the Test4Theory project aka T4T, some of you already know me. We all know and accept the fact that every new project has problems in the beginning and we all know that good projects do what they can to fix those problems. One of the cardinal rules in the BOINC community is that a project absolutely must not steal CPU cycles you have allocated to other projects. T4T has broken that rule. The admins know they are stealing and have refused to do anything about it for over 6 months. Why? Because they like the extra CPU cycles and because they don't know how to get more CPU cycles through honest means.

Recently they proposed testing a new application that would alleviate the problem but they will not install the new server code their new application requires. Without the new server code the application will not function properly which will allow them to say "sorry, the new application failed the test so we must continue with the current application". Yes, they have sabotaged the test application.

At one time I thought they were making an honest effort to fix the problem and be a "good project". Now I see I was wrong. They have no intention of changing their ways and their lies, lame excuses and theft of CPU cycles from other projects will continue. I am ashamed to have been part of their project. I don't want my name associated with T4T any longer and I present this information to the BOINC community so that you can avoid being another one of their victims.

Exactly how do they steal CPU cycles? Their application is actually a wrapper that starts/stops/suspends a virtual machine that does the actual crunching. The wrapper starts the virtual machine but does not suspend it in spite of the fact BOINC manager indicates it has been suspended. Everything appears normal and you don't even know the virtual machine is still running unless you look very carefully. Most volunteers assume the project is honest so they don't check and look carefully. The virtual machine runs at normal priority which means it does not relinquish the CPU for your other BOINC projects or for most of your personal computing needs the way a normal BOINC task does. So do the math... the task doesn't suspend and it runs at normal priority... that adds up to a lot of CPU cycles stolen from your other projects.

A fix for this problem has been available for many months but they have steadfastly refused to implement the fix citing one lame excuse and lie after another. Avoid T4T like the plague.

I've placed this information on many project forums and will place it on many more. Some of you might call that spamming but I think what T4T is doing is atrocious and I am convinced it is necessary to spread the word as quickly as possible which means as many forums as I can. I am not a spam bot, I post manually. Obviously I can't return to all the forums to discuss the issue so if you want more info/discussion please drop in to the T4T forums. This is NOT a ploy to get you to join T4T in fact I am advising that you NOT join T4T.

Profile NATE1
Avatar
Send message
Joined: 4 Aug 12
Posts: 37
Credit: 1,065,899
RAC: 0
Message 357 - Posted: 24 Oct 2012, 10:42:25 UTC

yes, the VM never stops running until the T4T app is done, 24 hours of run time on the app. so if the app is on your system 7 days the vm is running for 7 days after boinc starts the app. and it does not matter what the state of the T4T shows in the boinc manager. the VM is still running, once it has been started..

T4T is one of the projects, and there is more than one. that you don't try to run with any other project on the same host.
In other words. you give T4T its' own host,

Profile Emmy&Oreo
Avatar
Send message
Joined: 27 Oct 12
Posts: 14
Credit: 31,460
RAC: 0
Message 399 - Posted: 28 Oct 2012, 19:12:37 UTC

Word has it ,"there's trouble at mill" or something rotten in the state of ... errmm ... T4T.
Pause that project!
____________
KWSN K9 Corps

frankhagen
Send message
Joined: 15 Jul 12
Posts: 48
Credit: 400,146
RAC: 0
Message 401 - Posted: 28 Oct 2012, 19:18:08 UTC - in response to Message 399.

Word has it ,"there's trouble at mill" or something rotten in the state of ... errmm ... T4T.
Pause that project!



been there, checked that...

Profile The Dreamer
Avatar
Send message
Joined: 14 Oct 12
Posts: 2
Credit: 133,855
RAC: 0
Message 431 - Posted: 17 Nov 2012, 13:28:25 UTC

Projects that use VINA are worse....the application uses all your CPUs, but doesn't say so...so it is stealing CPU from other running projects, or CPU not allocated to BOINC, whenever it is active. And, being less nice about using just spare CPU cycles. Especially, if you have BOINC running all the time, but not to use all CPUs (IE: 3 of 4...it'll be using 3, while allowing two other projects to run trying to use 1 CPU each....But, BOINC shouldn't be trying to use 5 CPUs)

And yet, I haven't seen anybody call them out.

The Dreamer
____________
You may be a dreamer, but I'm The Dreamer, the definite article you might say!

swiftmallard
Avatar
Send message
Joined: 28 Jul 12
Posts: 30
Credit: 219,821
RAC: 0
Message 432 - Posted: 17 Nov 2012, 13:50:24 UTC
Last modified: 17 Nov 2012, 13:53:34 UTC

I have run other projects, CPU & GPU, simultaneously with FH@H and have had no problems with cycles being stolen.

Profile The Dreamer
Avatar
Send message
Joined: 14 Oct 12
Posts: 2
Credit: 133,855
RAC: 0
Message 461 - Posted: 17 Dec 2012, 16:58:00 UTC

Must only steal on Linux, which is all that I have.

So, I'll just quit this project.

The Dreamer.
____________
You may be a dreamer, but I'm The Dreamer, the definite article you might say!

JRP2706
Send message
Joined: 4 Aug 12
Posts: 1
Credit: 61,072
RAC: 0
Message 550 - Posted: 3 Mar 2013, 10:32:23 UTC

I have been trying T4T on and off for over a year now and initially it behaved as described by original poster, but seems to be behaving 'better' since the latest release of Oracle VirtualBox (4.2.8).

It seems to pause properly as per BOINC standards, just not on the specified cycle time, in my case 60 minutes.

I will keep trying it and report back in due course.

Cheers

mikey
Avatar
Send message
Joined: 21 Jul 13
Posts: 68
Credit: 1,289,610
RAC: 836
Message 826 - Posted: 23 Jul 2013, 16:10:39 UTC - in response to Message 432.

I have run other projects, CPU & GPU, simultaneously with FH@H and have had no problems with cycles being stolen.


Could this be why my Rainbow rac is decreasing recently?

mikey
Avatar
Send message
Joined: 21 Jul 13
Posts: 68
Credit: 1,289,610
RAC: 836
Message 828 - Posted: 25 Jul 2013, 13:39:17 UTC - in response to Message 826.

I have run other projects, CPU & GPU, simultaneously with FH@H and have had no problems with cycles being stolen.


Could this be why my Rainbow rac is decreasing recently?


No it seems since I started here my Rainbow rac is actually RISING, sorry for the confusion!! It seems it was POEM that was causing the decrease, probably the overhead with each project.

Profile Ex_Brit
Avatar
Send message
Joined: 3 Oct 13
Posts: 103
Credit: 16,743
RAC: 0
Message 1030 - Posted: 11 Oct 2013, 12:02:20 UTC

As far as I know this issue is now dead. I have T4T and Climate running happily together in VB.

Message boards : Cafe : rogue project: Test4Theory@home, don't join


Main page · Your account · Message boards


Copyright © 2017 Dr Anthony Chubb