This app definitely uses FP64, and to some extent even Tensor cores (if available). I was seeing very fast throughput on my Titan V, easily 3-6x faster than high end RTX cards like 3090s or 4090s
I know that the apps are OpenCL, but I wasn’t sure if that algorithm name “ocl[n]” was supposed to be referencing openCL directly or if it coincidentally was named ocl referring to something else. Like if there was some standard algorithm naming syntax in the maths world that I was ignorant to...
Stefan,
what is meant by the terms "ocl[n]" does the number n hold any significance other than an identifier?
does o-c-l mean anything in particular? does this reference "OpenCL", or are these just internal names given to the different algorithms in use in these various apps? can you expand...
no this isn't correct. you didnt use raid that much in those 30 years i guess?
raid 0 is striped, you get double the space and no parity
raid 1 is mirror, you get half the space and two copies of the data.
if you want raid10, you'll need 4 disks minimum in pairs. still only get half the space...
the answer is simple. EPYC does not support any kind of RAID, it does not have the hardware. that's why you can't find anything in the BIOS or manual about it.
you need to add a hardware RAID card or run a software based solution.
It’s different on the 4090 too. You are just still crunching older tasks. Old tasks are about 1600s new tasks about 2400 sec on 4090
And a quick look at your 4090 tasks clearly shows some of them running in the 2400s range, so yes you are seeing the slowdown too.
My focus is always on multi-GPU more than raw CPU performance, and I personally don't really care for PG or other number theory type projects. so that's why EPYC Rome/Milan is such a great fit for me. 7x GPUs without bifurcation, no problem :) the CPU projects I contribute to (mostly universe...
looks like they built the new TR on SP6 (sTR5), which it more similar to SP3, and SP3 coolers will probably work on it based on the pics (looks identical in size to SP3 to me)
I'd love to see a head to head of the TR Pro 7995WX vs the EPYC 9654.
same zen4 cores
same L3 cache
8ch 5200 vs 12ch...
not exactly, the board doesnt *need* gen4. you just need to explicitly set the lane speed to GEN3 in the EPYCD8 BIOS when using the Rome CPU.
if you had a Naples CPU, you wouldnt have had this problem.
I'm not sure if the SM H11 board has this problem. the Auto setting might work correctly to cap at GEN3.
I've had gen4 cards in my H11DSi with Rome CPUs and don't recall this ever being a problem. but it was a problem on all my EPYCD8 boards with gen4 GPUs. BIOS bug on a "$500 server board"
show me where i said it's "because it's a server motherboard". that doesnt make any sense.
i said it was a problem with YOUR motherboard. it's a problem with the EPYCD8 when used with a Rome processor and a BIOS misconfiguration
I think you still don't see the big picture. the reason it would...
the GPU fans don't spin because the card isn't working hard enough to need to spin. all modern GPUs act like this with zero RPM fan modes, which is baked into the GPU fan controller firmware and again not the root cause of your issue. it's only a symptom. the fan error itself is not causing any...
You’re misinterpreting the article. You really don’t understand how GPUs work at all. What you’re suggesting is bordering on some kind of conspiracy. The article is basically saying that they are taking these high power GPUs and using them for AI workloads. Which is what a lot of people are...
That article has nothing to do with your issue.
Device manager is showing you a bunch of devices for which you haven’t installed drivers. This is also unrelated to your issue.
i mean, from your screenshot it looks like it's not running windows 10 "no problem" since it doesn't detect the 4090 at all. the problem is not the OS. you are not understanding the big picture here. what's different between the 4090 and a titan V that might be a clue?
i didn't say the...
probably not the issue here. the system it's running on (single EPYC 7542) is only a 32c/64t part.
maybe some kind of motherboard problem or maybe even a GPU problem (assuming he didnt already test it in a known working system) mark should check the logs for pcie errors or other errors...
it might help marginally, but watch for memory errors pushing it too far. I pretty much only run the memory clocks at whatever offset gets them to P0 clocks. for Ampere GDDR6X that's +500, for Turing GDDR6 that's +400. not sure how much the 4090 is penalized in P2 vs P0.
also the BRP7 app seems to be heavily memory bandwidth limited, which explains why a 4090 isnt massively faster than a 3090/3080ti. it's faster, but not a lot, and not by the amount you'd expect.
the O3AS app has gone through a few iterations. I think as of this post, you were already trying the latest one, but for a little background and context i'll try to explain the behavior or best practices.
after the application had been solidified, it was basically running equal time chunks for...
No rush on the app Stefan. I appreciate you working on it :). Having a native app without broken behavior in the string length of the device name will be a godsend for everyone.
are you the data point in Ohio? looks like all of your readings are out of wack.
what is the firmware version of your detector? (in the detector menus they call it revision)
as far as i can tell, Krzysztof is the common link between all Radioactive, BOINC@Poland, and even Universe@home.
and he's been MIA for many months now.
Universe's security cert will expire on November 25th. not looking good for Universe either...
ok, I'm trying out your earlier idea of running BOINC under wine.
seems to be working (with a little extra CPU used to run the manager under wine for some reason) and no more shared mem message. we'll see if it shows up on the map
what are "trickles" and what do they do? and how would they be transmitted to the project in a way that might prevent display on the map?
in researching the error message, the only thing that seemed to make sense was this note from the boinc docs:
the closest i could come to figuring out...
for some reason, despite entering everything correctly and submitting validating results with the correct amount of credit, my Linux+wine systems never show up on the map. I'm not sure if it's a consequence of BOINC running the app in "standalone mode" or not, as that seems to be the only...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.