this post was submitted on 28 Oct 2023
306 points (98.4% liked)
Technology
60052 readers
3048 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yes and no, it's not about the instruction set size but about general overhead.
The x86 architecture makes a lot of assumptions that require a bunch of circuitry to be powered on continously unless you spend a ton if effort on power management and making sure anything not currently needed can go into idle - for mobile CPUs there's a lot of talk about "race to idle" as a way to minimize power consumption for this exact reason, you try to run everything in batches and then cut power.
The more you try to make ARM cover the same usecases and emulate x86 the more overhead you add, but you can keep all that extra stuff powered off when not in use. So you wouldn't increase baseline power usage much, but once you turn everything on at once then efficiency ends up being very similar.