rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7445
Credit: 42,730,867
RAC: 0
There will be a name change of the project due a not permitted name from the website operator.
I know it is a bit of a work, but you may also remove the unpermitted name from all message posts where it occurs. Sorry.
Then you must remove this from all websites, statistic pages, this is free expressions.
/ 
Reply
Quote
Then you must remove this from all websites, statistic pages, this is free expressions.
You are correct.
As long as the name is removed, from the projectlist and from the server aswell the badges that must meet his demands. We are afterall, as you mention allowed the freedom of speech.
Keep up the good work and stay strong :)
and now back to helping GIMPs :)
/ Reply
Quote
DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 101,340
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 101,340
There will be a name change of the project due a not permitted name from the website operator.
Which name is not permitted?
Who gives the permission?
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7445
Credit: 42,730,867
RAC: 0
There will be a name change of the project due a not permitted name from the website operator.
Which name is not permitted?
Who gives the permission?
GPU72 and I got no permission to use it while I have asked. I can only use the name until 07th of April.
/ Reply
Quote
DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 101,340
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 101,340
o.k.?
https://www.gpu72.com/
We can name it GPU95 because 95 bit is the limit of this software ;)
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7445
Credit: 42,730,867
RAC: 0
o.k.?
https://www.gpu72.com/
We can name it GPU95 because 95 bit is the limit of this software ;)
I have changed it to Trial Factoring, the app name should then TF
/ Reply
Quote
How long will the tasks be and how much will the tasks weigh my GPU? Like if they are very taxing or they're moderate or they're light.
1h+ with 99%
I would just like to give an update on how long it takes to run a task on a Windows machine. It took 3 hours 13 mins and 33 seconds of runtime to complete GPU72_77-78_batch1_wu_3738_3 On a RTX 2070
/ Reply
Quote
I've had some run 18+ Hr's aborted a few. Seems like the ones with GPU72_77-78 name take forever, the GPU72_73-74 named Wu's run shorter
/ Reply
Quote
I've had some run 18+ Hr's aborted a few. Seems like the ones with GPU72_77-78 name take forever, the GPU72_73-74 named Wu's run shorter
Dear STEVE
Yes they are very long. We will most likely not see that long workunits for a while. The logic is like follows, if you spent 18 hours on a 77-78 bit at n=105M, then:
77-78 bit = 64800 s
76-77 bit = 32400 s
75-76 bit = 16200 s
74-75 bit = 8100 s
73-74 bit = 4050 s
72-73 bit = 2025 s
When you double n to n=210M the test time will look like this:
77-78 bit = 32400 s
76-77 bit = 16200 s
75-76 bit = 8100 s
74-75 bit = 4050 s
73-74 bit = 2025 s
72-73 bit = 1012 s
71-72 bit = 506 s
70-71 bit = 253 s
We will most likely startout with the 70-71 bit tests that takes you about 4 minutes per test (these will as we nears nMax take you about 1 minute).
The rule of thumb (not 100% exact) is that as bit goes up 1 bit, testing time doubles compared to previous bit. When n doubles testing time is cut in half. We will double 3 times, so a 77-78 bit test will at nMax take about 8100 seconds on your machine.
nMax=1,000,000,000 (more or less)
nMin=110,000,000 (give and take)
Take care, stay safe and please do not abort any tasks, even if they seem to take forever, because credit is adjusted accordingly and you will eventually complete the test, even if you have very old gear :smile:
/ Reply
Quote
please do not abort any tasks, even if they seem to take forever, because credit is adjusted accordingly and you will eventually complete the test, even if you have very old gear
Okay I'll let them run ...
/ Reply
Quote
Okay I'll let them run ...
Great. Now you made me curious, does the progress bar in BOINC not show the actual progress that mfaktc has made?
I'm asking, because I can see that you have actually had progress on all the workunits you aborted. Sorry to break your heart, but the progress looked like this:
http://srbase.my-firewall.org/sr5/result.php?resultid=387853299 4.9% complete after 01 h 06 minutes
http://srbase.my-firewall.org/sr5/result.php?resultid=387852880 90.3% complete after 1 d 08 h 05 m
http://srbase.my-firewall.org/sr5/result.php?resultid=387965108 66.4% complete after 18 h 08 m
So did BOINC show 0% complete or what did BOINC show?
/ Reply
Quote
BOINC Showed 100% Done, right now I have 2 Wu's on 2 different Box's showing 100% done also, both are at about 4 Hr's run time ...
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7445
Credit: 42,730,867
RAC: 0
BOINC Showed 100% Done, right now I have 2 Wu's on 2 different Box's showing 100% done also, both are at about 4 Hr's run time ...
Check the stderr.txt. You can see how much you have done yet.
/ Reply
Quote
Shows 100% w/5:13 run time done per BOINC but only 57.9% according to the stderr.txt
Apr 10 10:46 | 2668 57.9% | 61.620 6h54m | 443.10 82485 n.a.%
/ Reply
Quote
The Progress bar is no where accurate. It gets to 100% fairly quick compared to the runtime of the WU, but then is there at 100% for a long time still computing until it is actually finished.
/ Reply
Quote
Maybe that should be in the intro post describing Trial Factoring or in the FAQ. It appears due to the slow move in the amount of unsent tasks, that we have had quite a few users cancel their work, due to them not thinking that they actually progressed. Would such a news or FAQ had made a difference for you STEVE? Would it have made a difference for you Bluestang?
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7445
Credit: 42,730,867
RAC: 0
The Progress bar is no where accurate. It gets to 100% fairly quick compared to the runtime of the WU, but then is there at 100% for a long time still computing until it is actually finished.
yes, this is a problem with the client/server. If the runtime is changing every time from short to long the server will take a while to adjust the estimated time by reporting the WUs.
/ Reply
Quote
Maybe that should be in the intro post describing Trial Factoring or in the FAQ. It appears due to the slow move in the amount of unsent tasks, that we have had quite a few users cancel their work, due to them not thinking that they actually progressed. Would such a news or FAQ had made a difference for you STEVE? Would it have made a difference for you Bluestang?
Probably not, I read where the Wu's should only take a few Hr's, so when they hit 18 Hr's I figured that was a few Hr's to long ...
/ Reply
Quote
It's always been like that from the start. Only difference now is the amount of time it takes to actually complete after it hits 100%. By far worse on AMD than NVIDIA. I think NVIDIA is pretty accurate as it looks like it tracks time properly with Progress Bar.
I thinks it's a good idea to put hat info out there so people don't abort. I knew that it was doing work still as my I look at my GPU utilization before doing anything drastic like aborting them after running for so long.
Also, is there ckeckpoints? If I have a power issue or have to reboot do I loose my current work up to that time or is there a checkpoint saved for it to go back to?
/ Reply
Quote
It's always been like that from the start. Only difference now is the amount of time it takes to actually complete after it hits 100%. By far worse on AMD than NVIDIA. I think NVIDIA is pretty accurate as it looks like it tracks time properly with Progress Bar.
I thinks it's a good idea to put hat info out there so people don't abort. I knew that it was doing work still as my I look at my GPU utilization before doing anything drastic like aborting them after running for so long.
Also, is there ckeckpoints? If I have a power issue or have to reboot do I loose my current work up to that time or is there a checkpoint saved for it to go back to?
I think you will find some of this information as already detailed in Frequently Asked Questions
/ Reply
Quote