Gizmodo: How Get the Most out of Your Graphics Card https://gizmodo.com/graphics-card-nvidia-how-to-use-it-maximize-it-1850623061 #fablesssemiconductorcompanies #graphicsprocessingunit #technologyinternet #graphicshardware #atitechnologies #graphicscards #nvidiaoptimus #overclocking #geforce #nvidia #gpgpu #amd

@md @bmi @bsi #TETRA's #Crypto is so #weak that it's trivial to crack with any modern #GPGPU, because it's #SecurityThroughObscurity makes all the #TEA versions as weak as #CSA on #DVB.

But then again noone pays me to fix it, so it's not my problem.

Spoiler: The proper fix is to abolish all #proprietary shit and demand a fully #OpenSource'd communications system, since everything else violates #KerckhoffsPrinciple and is thus inherently and unfixably insecure by design!

WebGPU — All of the cores, none of the canvas, https://surma.dev/things/webgpu/.

An excellent article explaining what WebGPU is, and how to use it to do computations not related to graphics. Kudos for the article, very didactic.

#webgpu #gpgpu

The feature I miss the most from Twitter on Mastodon is quote tweets, explicitly of my own for the use case of related but divergent technical threads.

Working on the #GPGPU && #AVX512 accelerated build of #PETSc to enable faster execution of #OpenFOAM as of now and all the relevant threads would have to be independent threads and hard to cross reference as new threads/tangents pop up.

Intel's Codeplay Announces oneAPI Construction Kit For Bringing SYCL To New Hardware
https://www.phoronix.com/news/oneAPI-Construction-Kit

"This open-source project aims to help ease bringing up SYCL on new processor/accelerator architectures, particularly around HPC and AI. The oneAPI Construction Kit also has a reference implementation for RISC-V."

#IamIntel #Intel #oneAPI #HeterogeneousComputing #GPU #GPGPU #HPC #AI #SYCL #RISCV

Zero in on Level Zero: An Open, Backend Approach to Compute Anywhere
https://www.intel.com/content/www/us/en/developer/articles/technical/zero-in-on-level-zero-oneapi-open-backend-approach.html

"Intel’s first implementation of Level Zero targets Intel GPUs. However, the vision and potential of Level Zero goes far beyond that. [...] The API is designed to work across a variety of compute devices, including CPUs, GPUs, Field Programmable Gate Arrays (FPGAs), and other accelerator architectures."

#IamIntel #Intel #oneAPI #HeterogeneousComputing #GPU #GPGPU #FPGA #HPC #AI

Kotaku: After Much Controversy, Nvidia Brings Back A Budget PC Graphics Card https://kotaku.com/nvidia-geforce-rtx-4070-budget-4k-ray-tracing-dlss-3-1850327485 #gaming #tech #kotaku #graphicsprocessingunits #computerarchitecture #computergraphics #graphicshardware #geforce20series #jensenhuang #videocards #nvidiartx #geforce #nvidia #turing #gpgpu #rtx

In slight need of spec/language lawyers: Reading this line ( https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_API.html#CL_DEVICE_MAX_MEM_ALLOC_SIZE), do you think:
A: that the minimum allocation of the max mem allocation flag is 1:4?
B: that the max allocation must be max(min(1024 × 1024 × 1024, 1/4th of CL_DEVICE_GLOBAL_MEM_SIZE), 32 × 1024 × 1024)

in other words, given a 16GB card, should the maximum allocation be 4GB, or should the minimum of the max allocation be 4GB?

#opencl
#sycl
#khronos
#HPC
#GPGPU

I wonder if the people that lived through the early days of computing (say, before the standardization of C) lived similar experiences to the ones we're leaving today in #GPGPU, this sensation that a unifying solution is possible, but remains “just” out of reach as vendors remain (at best) cautious about fully supporting higher level standards, preferring to push their own solutions (sometimes veiled in a pretense of standardization) to varying degrees of success.

Why am I so interested in #SYCL for #GPUSPH? (See also my nudge nudge wink wink at @sri <https://fediscience.org/@giuseppebilotta/109942222462252885>)
Because SYCL is today the best bet we have at a unified #GPGPU API, and introducing such a backend would have great potential for our aims of “universal hardware support”.

@fuchsiii @nano that's one of those PCIe Extenders that use a USB 3.0 cable to mux a single PCIe x1 lane to an extension board.

AFAIK they barely deliver PCIe x1 1.0 speeds [250 Mbit/s] so not really useful for anything but #Mining and #GPGPU tasks.

One of the reasons why I still haven't done my long-promised mini-thread on #GPGPU is that every time I find some time to brainstorm the thing I get indescribably angry at vendors, and I realize that the tone of the thread would really take a bad turn I would rather not have it have.
Mind you, I love the field, but I have a lot of pent-up frustration due to how much vendors keep (intentionally or not) making things much harder than they should be.

@ProjectPhysX ...but beyond crashing all the time, are they pleasant to program for #GPGPU?

RT @aqro@twitter.com

The Spellcaster, my new #webgl experience using #threejs, #gsap and a ton of #shaders. I guess you got the reference. 🧙

💫 https://adinunz.io/spellcaster/

#gpgpu #realtime #glsl #particles #trails #parametriccurves #instanced

🐦🔗: https://twitter.com/aqro/status/1594420254263869441

Now that our instance has a higher size limit for toots, time for a re-#introduction. This time with more hashtags!

Hi! I'm Jeff. :blobcatwave:

I've been a software engineer since around 1999 I guess. I started with #WebDev back in the early days of applets, DHTML, and Flash. I've since moved on to #FullStack work on just about anything that has a compiler or an interpreter. I've even recently dabbled in #PCB design and #3DPrinting.

My software specialties are in high performance computing #HPC, #GPGPU, and #ComputationalChemistry. Although I usually enjoy any programming problem with a good challenge to it. I spent waaay too much time in school and got all the degrees in computer science. I still work in #academia part-time writing research software.

My favorite programming languages at the moment are #Rust and #Kotlin. Although, I've spent a lot of time writing #Javascript lately. With the right tooling it's not completely terrible.

More recently, I've been interested in online #privacy, #cryptography, and #SocialNetworks.

RT @aqro@twitter.com

The Spellcaster, my new #webgl experience using #threejs, #gsap and a ton of #shaders. I guess you got the reference. 🧙

💫 https://adinunz.io/spellcaster/

#gpgpu #realtime #glsl #particles #trails #parametriccurves #instanced

🐦🔗: https://twitter.com/aqro/status/1594420254263869441

@anteru

FWIW, I really appreciate the amount of work #AMD is doing on #GPGPU, and doubly more so for its #FLOSS nature, but from the outside it seems at times a bit ... “dispersive” (OpenCL, HSA, ROCm/HIP ...) which for a company with limited resources only serves the effect of discouraging developers due to a perceived unreliability («will this solution still exist next year? will my hardware still be supported?»).

@ashwinvis

i've heard from multiple sources that scientific computing today is not bounded by performance time for doing arithmetic but by memory access time and throughput. is there some resource (paper/blog post) that someone here can refer me to so that i can understand it deeply #gpu #gpgpu #cuda #memorylatency

RT Sergey Borovikov
Made an example of particle system that responds to a mouse movement and touches by GPU computation in a vertex shader. It includes a bit of physics with velocity manipulation.
Via @CodePen and @threejs
Link:
#webgl #gpgpu #shader #glsl
http://codepen.io/foretoo/full/XWqqgOb

:sys_twitter: https://twitter.com/sergthere/status/1576656573404876800

I'm still preparing my post series on #GPGPU, but in the mean time you can read some about in our most recent published paper:
“A numerically robust, parallel-friendly variant of #BiCGSTAB for the semi-implicit integration of the viscous term in #SmoothedParticleHydrodynamics”, freely accessible for the next 50 days from this link:
https://authors.elsevier.com/a/1fN8C508HsZiG