A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
This is an extremely misleading headline.
From the abstract:
In other words... This method of computation could save 95% of the energy spent on floating point multiplication (and save 80% on dot products)... Not 95% of total energy.
I don't see any analysis of how this would impact total energy.
I'd say it's not just misleading but incorrect if it says "integer" but it's actually floats.
Good point. Though, the vast majority of ML training and use is tensor math on floating points, so largely dot and cross products, among other matrix operations.
Came here to say that a 95% reduction in energy consumption will only greenwash a corresponding or larger increase in usage — but yours is of course the correct response! 👏👏👏
But... Isn't that kind of the point? Slashing computational cost so that we can deploy that stuff wherever it's needed without a tenfold increase in the world's energy bill?
Whether we should do that at all is a very different question.
"Wherever it's needed" is the operative term here, isn't it? Looking at how it's already being implemented, nobody seems to bother asking whether "AI" is really needed.
Personally, I find myself in a bizarre situation.
I have some open source ""Ai"" solutions that I find really really nice and helpful e.g. the image search in Immich, or LanguageTool which bills itself as an AI spellchecker.
At the same time I am horrified at the stupidity underlying 99% of big tech AI stuff that gets wall street hot.
That's the difference, isn't it? People can use "AI" to make simple little things easier. Corporations want it to replace and automate the jobs of swathes of the workforce. It's the latter that is the "growth market", and the one that eats the most power.
That wouldn't be so bad per se... Many improvements in human conditions have been achieved by automating stuff and kicking people out. Think of the green revolution.
The problem is that the use case here is to massify the production of literal shit, like clickbaity articles on social media content, or ever larger volumes of advertisement. Those jobs don't need to be replaced, they just need to go away for good.
Are we really going to use an AI to write motivation letters from a list of bullet points, to send it to an HR that will condense it into a list of bullet points using AI? Seriously?
Improving the technology behind AI will only increase the return on investment per watt, so you'll want to spend even more on it than before. This would more than likely increase the energy demands (assuming it doesn't turn into vaporware).
Isn't this basically just the old trick of estimating (x * y) as (x + y - 1) when x and y are somewhat close to 1?
3 * 2 = 6
3 + 2 - 1 = 4
So, close enough? How "close to 1" are you talking about?
Seems pretty good for 1.1 x .9, and for .9 x .8
I guess values must be pretty close
I wonder what other applications this might have outside of machine learning. I don't know if, for example, intensive 3d games absolutely need 16bit floats (or larger), or if it would make sense to try using this "additive implementation" for their floating point multiplicative as well. Modern desktop gaming PCs can easily slurp up to 800W.
I have a vague memory of a 3D engine from the 1990s using an approach like this, but I'm not entirely sure.
I think you're thinking of the famous fast inverse square root algorithm from Quake.
With respect to the top comment, the only reason 3d graphics are possible (even at 850W of power consumption) is due to taking a bunch of shortcuts and approximations like culling of polygons. If its a reasonable shortcut it either has or will be taken.
