Our latest blog by Dairsie Latimer, Technology Fellow at Red Oak Consulting, explores a critical question the industry is beginning to confront: are we waiting for AI’s FFT moment, or are we about to hit the limits of energy and infrastructure?
👉 Read the full blog: buff.ly/v0E4bTY
#AI #HPC
Elbows up, Canada.
Next HPC Club Meet - March 12th!
We are happy to share that Martin Callaghan, Principal Consultant at Red Oak Consulting, will be sharing insights on 'Effective Allocation of GPU Resources' at #HPCClub.
🔗 Reserve your spot: buff.ly/DqpzKQ5
#HPC #AI
Brilliant - that’s exactly what I just read!! 🤣
That’s a hot mess and a half. I couldn’t make head nor tail of half of it and the other half I disagreed with! 🤪
I wondered when we'd see more snow clearing action from Dr Cuff! 😀
😂And taught me to sweat the cycles in inner loops (and later to be view optimisation as a system level exercise)!
It also set me up for an interesting career doing everything from writing OpenGL implementations to CPU microcode and everything in between.
More people need to sweat the detail IMOHO!
In many instances I think it's less about language choice and more a lack of knowledge of the end-to-end nature of most workflows. Eliminating wasteful/nugatory steps (keeping stuff in memory etc) usually does more for efficiency and performance. Same category as making smart algorithmic choices!
Moore's Law (and a desire for built in obsolescence) has lots to answer for in terms of excusing inefficiency in software engineering and making users apparently apathetic toward performance. The flips side of that is we are all accepting inefficiency in the systems and software we use all the time.
If my work in HPC and AI has taught me anything is that most CS grads today simply don't have the low-level knowledge and in many cases the 'need' to know because we are apparently living in a MIPS rich era (I started programming on a ZX81).
100% agree that understanding the energy/carbon footprint of your code is something that we should all care about - but less convinced that it's all about the language. (I assume you have python squarely in your sights?)
If you haven't already @sebaaltonen.bsky.social has posted extensively on his journeys in AO land!
In our latest blog, we explore how Molecular Dynamics simulations work, their real-world applications, and the future direction of this field.
Read more: https://buff.ly/41aDc6F
#MolecularDynamics #ComputationalScience #MachineLearning
Dairsie Latimer, Technology Fellow, discusses how AI Export Control Frameworks might impact the #AI and #HPC sector in our latest blog.
Read more: https://buff.ly/411k6hO
Let us know your thoughts in the comments below⬇️
That’s actually quite impressive!! What’s the UPS strategy?
Would be nice. Hope you had a pleasant festive season and that you have some plans for the 2025 that brings smile !!
Code written with box characters used on old old software to make fake UIs
You’re still arguing about tabs vs. spaces? May I present…
Elmo covers quite a few bases I suspect. For me Arthur Woofington gets me out and about ‘every day’, keeps my feel warm when it’s cold and is an adorable and occasionally goofy companion!
That’s my Lab Arthur and he’s keeping me company on the sofa right now!
Hey there are other dog lovers on here you know! 😀
I think my #HPC Secret Santa was fishing for a reaction … 😂
Elmo is cool - it’s Boof who’s on fire !!
Is is a good dream or a nightmare when the alarm wakes you up in the middle of worrying about decomposing DGEMM and DTRSM across multiple accelerators? #HPC #nightmares
Welcome! Nice to see you round these parts!
It’s an absolutely fascinating read.
It’s on my festive watch list.
A die photo of the Pentium processor with the main functional blocks labeled including the caches, instruction fetch and decode, integer execution, and floating point. The image consists of complex patterns of rectangular regions in reddish and brownish colors. The image zooms in on a small part of the floating point unit giving a detail of an adder and PLA circuit.
Intel launched the Pentium processor in 1993. Unfortunately, dividing sometimes gave a slightly wrong answer, the famous FDIV bug. Replacing the faulty chips cost Intel $475 million. I reverse-engineered the circuitry and can explain the bug. 1/9
This Christmas tree tickled my inner gamer … (www.reddit.com/r/gaming/com...)
Sounds potentially rather messy! Fingers crossed for decent coverage!
I once helped a friend plaster a small house. It was six rooms in total and by the time we got to the fourth we gave up and ended up chipping off the plaster from the first two rooms before getting a pro in to do it properly! 🤣
If it’s any consolation I put shelves up yesterday and managed to make the sockets who’s conduit I thought I had very carefully worked around stop working! 🤪
