Technology

58115 readers

4078 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

641

Generative AI is reportedly tripling carbon dioxide emissions from data centers (www.techradar.com)

submitted 3 days ago by JRepin@lemmy.ml to c/technology@lemmy.world

69 comments fedilink hide all child comments

cross-posted from: https://lemmy.ml/post/20289663

A report from Morgan Stanley suggests the datacenter industry is on track to emit 2.5 billion tons by 2030, which is three times higher than the predictions if generative AI had not come into play.

The extra demand from GenAI will reportedly lead to a rise in emissions from 200 million tons this year to 600 million tons by 2030, thanks largely to the construction of more data centers to keep up with the demand for cloud services.

you are viewing a single comment's thread
view the rest of the comments

[–] Ragdoll_X@lemmy.world 35 points 3 days ago

I remember when scientists were more focused on making AI models smaller and more efficient, and research on generative models was focused on making GANs as robust as possible with very little compute and data.

Now that big companies and rich investors saw the potential for profit in AI the paradigm has shifted to "throw more compute at the wall until something sticks", so it's not surprising it's affecting carbon emissions.

Besides that it's also annoying that most of the time they keep their AIs behind closed doors, and even in the few cases where the weights are released publicly these models are so big that they aren't usable for the vast majority of people, as sometimes even Kaggle can't handle them.