Posts by -= Vyper =-

1) Message boards : Number crunching : Linux CUDA 'Special' App finally available, featuring Low CPU use (Message 1902086)
Posted 20 Nov 2017 by Profile -= Vyper =-
You can also check my host here to add it to the mix..

I don't really see the Point for anybody here to be upset over high amount of inconclusives. As long as there are alot of other applications that the particular host gets matched to and the host is fast the higher the inconclusive rate it would be until the others Catch up and the workunit is either invalid/errored out or validated.
Ofcourse we need to monitor the values etc but as stated earlier the main story of the inconclusive rate is still the out of order sorting of the Linux Cuda app (if i haven't accidently missed somewhere that it has been fixed) and how fast the particular host is..

For instance.. Tbars Host has alot of 1050/1060s and those are faster than in my case 750Tis.. My inconclusive rate is 3,5% and Tbars is 4,7% and Petris host has for the moment 4,6% of inconclusives .
Tbar is running: x41p_zi3v , i am running x41p_zi3x-32 and Petri is running x41p_zi3xs3.. So we can't really compare apples/oranges there but there seems to be an indication that Petris app "seems" to be even more on spot and conclusive for the moment than Tbars..

And as i said the reason i Believe my inconclusive rate is lower is that my GPUs are slower so they don't turn back that much in time to get a large pending que compared. Tbars pending/inconclusive ratio is 26.9 , my is 19,7 and Petris is 22,1
I Think there is a correlation between the pending/inconclusive rate if compared with the same application to give the inconclusive rate in percentage. I suspect that if the host is faster the P/I ratio should rise and thus the I percentage likewise if compared!
For example if my host had even slower GPUs the P/I should go down somewhat further to perhaps 17 and i Believe that the I percentage would drop perhaps to 3,35%. So in my mind we really cant compare the I percentage on which app is better or not fully to that extent that this discussion is leaning to.

What we all should be concerned of is make sure the app matches the original stock CPU application to the max and keep the invalid/error rates down that really shows that the particular application run is not in par with the rest. Period!
Inconclusives is just a hint/guideline but i belive that host speed must be taken in consideration aswell as only to look at the I percentage value.

Insert alot of unnecessary wait states and slow down the application and the median value of I most certainly would decrease aswell..

Most importantly now, is my thinking and assumption wrong here regarding adding host speed to the mix? Give me your thoughts and please keep this thread less hostile than it has turned out to be lads..
2) Message boards : Number crunching : Linux CUDA 'Special' App finally available, featuring Low CPU use (Message 1894808)
Posted 12 Oct 2017 by Profile -= Vyper =-

What to do about this? Running Mint 17.3 with Nvidia 384.90..

process exited with code 127 (0x7f, -129)
../../projects/ relocation error: ../../projects/ symbol _ZTVNSt7__cxx1119basic_istringstreamIcSt11char_traitsIcESaIcEEE, version GLIBCXX_3.4.21 not defined in file with link time reference

3) Message boards : Number crunching : Linux CUDA 'Special' App finally available, featuring Low CPU use (Message 1890432)
Posted 17 Sep 2017 by Profile -= Vyper =-
I agree aswell with both TBars and petri33s statement.

A noisy overflowed WU is what it is.. There is a reason for this limit set and if they change it in the future they will and they will modify the original code tree to include perhaps 60, 100 or even 500 signals?! Who knows.
But as they both say.. If it finds thirty signals within a few seconds, then consider it "aborted" instead in everyones minds then it would be easier to understand the terminology of the meaning of "30 signals found , overflow triggered".

My 2 cents!
4) Message boards : Number crunching : Tesla K80 on Google Cloud platform - not recognised (Message 1882113)
Posted 4 Aug 2017 by Profile -= Vyper =-
Try teamviewer.. It worx flawless..
5) Message boards : Number crunching : Ryzen on Linux (Message 1880059)
Posted 24 Jul 2017 by Profile -= Vyper =-
My Ryzen isn`t running very hot.
I usually have 51° to 55°C running 6 instances on CPU plus GPU.
I have a Noctua D15 installed and its not even running full load atm.
Of course you are overclocked with your 1700 which is different.

I have Linux running on a 64 GB USB 3 stick. That was just 60 Bucks.
It runs smoothly and very fast.
You just need some time to read thruough everything.

A warning is at a place here (Eine kleine warnung).

Boinc and the seti app both write to disk (USB). BOINC writes just as it is told to do in the user interface (once in a minute or so).
The (GPU) App writes checkpoints hundreds of times a second unless it is modified in the source code to not to do so.
Please make a backup for your own sake.

My NV code will not do any checkpoints in the next version. A restart of a task will start from 0% but that is not so a big loss, is it?

Viel Grüss,

This is solved by Reading this and check the section for Approach 2!
6) Message boards : Number crunching : Linux CUDA 'Special' App finally available, featuring Low CPU use (Message 1879431)
Posted 21 Jul 2017 by Profile -= Vyper =-
Hi TBar..

Just wanted you to know that i've switched my Quad 750Ti to your application now. If you perhaps want a machine to monitor missbehaviour within the executable but i presume that wont be much of an issue.

Thanks for keeping it up!
7) Message boards : Number crunching : Linux CUDA 'Special' App finally available, featuring Low CPU use (Message 1875361)
Posted 27 Jun 2017 by Profile -= Vyper =-
How do we know that the CPU portion of latest code isn't effected by sporadic errors when running Hyperthreading enabled?!
Has anybody run tests with and without HT on Skylake and Kaby Lake computers?!
8) Message boards : Number crunching : Debian Project Warns: Turn off Hyperthreading with Skylake and Kaby Lake (Message 1875360)
Posted 27 Jun 2017 by Profile -= Vyper =-
Thank u for the heads up!!! +1
9) Message boards : Number crunching : Linux CUDA 'Special' App finally available, featuring Low CPU use (Message 1875358)
Posted 27 Jun 2017 by Profile -= Vyper =-
BTW, can Petri's app run on such GPUs (mobile ones) ?:

NVIDIA GeForce 940MX
NVIDIA GeForce 820M

This is what i've found out:

"The executable is version zi3t2b and it can be run on sm_35, 50, 52, and 61. (750,780,980,1080 and likes).
With 1 Mb of GPU ram you need -unroll 1. Other can use -unroll autotune.
Use -bs to reduce CPU usage.
Set -pfb to 8, 16 or 32."

EDIT: 820M seems out of luck.. CC2.1 only but the 940MX seems to work CC50
10) Message boards : Number crunching : CES 2017 -- AMD RYZEN CPU (Message 1847796)
Posted 10 Feb 2017 by Profile -= Vyper =-

Oh is that so! If this is true then this could be a cpu crunchers wet Dream..
11) Message boards : Number crunching : Transferring work units from a dead laptop (Message 1841366)
Posted 11 Jan 2017 by Profile -= Vyper =-
Was it a Windows XP computer?
12) Message boards : Number crunching : Linux CUDA 'Special' App finally available, featuring Low CPU use (Message 1836823)
Posted 18 Dec 2016 by Profile -= Vyper =-

But i'm using 16.04 on one of my hosts. Worked like a charm!
Though i started with installing only the server version with nothing more than OpenSSH server to continue from there though.
Good that more ppl are jumping the Linux bandwagon for eeking out the most of their hardware at the moment.
13) Message boards : Number crunching : Linux CUDA 'Special' App finally available, featuring Low CPU use (Message 1834772)
Posted 8 Dec 2016 by Profile -= Vyper =-
TBAR: Have you compared the speed of your compile compared to Petris different builds? Good that the invalid rates are down but as we all know by know we cant eliminate the way the validator thing works either.
The more you produce faster the more inconclusive ratio that host seem to have until it vanishes of.

What i now write below is my theory:

With that i mean, if you have a slow host that doesn't process that much WUs per day you tend to end up crunching units that your wingman already has crunched. If the validator compares the work of a (I call it Petri Cuda) WU and compare it to the other that has been crunched already you get a validation pass and both get rewarded credits and the WU soon is cleared from the system (Cannot find the WU) as we can see when they have been processed and thus the invalid ratio is low!

When you have the opposite a ultra-speedy system that crunches thousands of WUs per day the more inconclusive you will get because that machine is so fast and returns the work first of them all and Waits for other computers to Catch up and when they start to return WUs and the overflowed results are pooring in so that speedy Machines inconclusive ratio will rise faster than others as well.

/End of Theory

What actually matters is ofcourse that the code does the work properly! Q ratio high as possible in various tasks, GBT, High/Low AR etc etc you all know that part but the value as Tbar refers to as "Consecutive valid tasks"
That one is the main thing to keep track of in my mind not the inconclusive part because the more parallel code the more inconclusives we will get wether it's an CPU, GPU , FPGA, PS4 yada.

Thanks for your work TBar and thank you Petri for going the brute force route of taking advantage of newer hardware that made this leap. Latest SoG is also speedy as hell! The 1080 if mine is utilized better than running multiple parallell Cudas now! Thank you Raistmer,Jason,Urs and all you Alpha/Beta testers and others that has contributed that has made that we're where we are at the moment! The list of ppl would get long.
14) Message boards : Number crunching : Spammers (Message 1830835)
Posted 16 Nov 2016 by Profile -= Vyper =-
Delete: Just tested.. From. -= Vyper =- (Is this bullshit for real with extreme amounts of letters in the name, why is it even possible in the first place? Who could have figured that you could write a novel here and it is allowed to have so many characters in the name. Lol
15) Message boards : Number crunching : Spammers (Message 1830834)
Posted 16 Nov 2016 by Profile -= Vyper =-
Omg! I tested and it worked! Lol! :D
16) Message boards : Number crunching : The wonders of Micro$oft Windoze (Message 1829935)
Posted 11 Nov 2016 by Profile -= Vyper =-
And this then?
17) Message boards : Politics : Hillary Clinton - the next president of America? (Message 1829266)
Posted 9 Nov 2016 by Profile -= Vyper =-
It seems to be over for Hillary now!

Trump is Trumphiant :P
18) Message boards : Politics : Donald Trump for President? (Message 1829265)
Posted 9 Nov 2016 by Profile -= Vyper =-
Lol! It seems done now!

The World just got more Trumpified! :D
19) Message boards : Number crunching : Monitoring inconclusive GBT validations and harvesting data for testing (Message 1827674)
Posted 31 Oct 2016 by Profile -= Vyper =-
So, why is the Intel build faster on the nVidia cards?

Nice find!
Maybe Intel Crippling is back again or something?! I don't know! I can only guess. They've done it in the past and may very well do so again :)
20) Message boards : Number crunching : Moore's Law illustrated (Message 1827036)
Posted 27 Oct 2016 by Profile -= Vyper =-
Lol, I've programmed Assembly and i loved it back in my Amiga Days. Workbench friendly assembly with correct calls to libraries! :)

Next 20

©2018 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.