this post was submitted on 26 Jul 2024
995 points (99.5% liked)

Technology

59157 readers
2123 users here now

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

Our Rules

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

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
995
There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any damage is permanent (www.theverge.com)
submitted 3 months ago by mox@lemmy.sdf.org to c/technology@lemmy.world
269 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] sugar_in_your_tea@sh.itjust.works 1 points 3 months ago

AWS' benchmark is about lambda functions, not compile workloads, which are quite different beasts. Lambdas are about running a lot of small (so task switching), independent scripts, whereas compiling is about running heavy CPU workloads (so feeding caches). Server workloads tend to be more of the former than the latter.

That said, I'm far less interested in raw performance and way more interested in power efficiency and idle and low utilization. I'm very rarely going to be pushing any kind of meaningful load on it, and when I do, I don't mind if it takes a little longer, provided I'm saving a lot of electricity in the meantime.