this post was submitted on 13 Oct 2024
54 points (100.0% liked)

Technology

37716 readers
326 users here now

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.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Jayjader@jlai.lu 4 points 1 month ago (1 children)

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.

[–] DdCno1@beehaw.org 1 points 1 month ago (1 children)

I have a vague memory of a 3D engine from the 1990s using an approach like this, but I'm not entirely sure.

[–] IrritableOcelot@beehaw.org 5 points 1 month ago

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.