Technology

59107 readers

5484 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

393

Intel's Meteor Lake CPUs are slower at single-core work than previous-gen models — new benchmarks show IPC regressions vs Raptor Lake (www.tomshardware.com)

submitted 10 months ago by kinther to c/technology

61 comments fedilink hide all child comments

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

[–] [email protected] 6 points 10 months ago (2 children)

it’s a matter of adding more threads

You can't ask 300 people to build a chair, and expect the chair to be finished 300x faster than if a single person would build it.

[–] Buddahriffic 5 points 10 months ago (1 children)

Also, to make it more accurate to what multi-threading does, none of those 300 people can see what the others are doing. And the most reliable ways of sending messages to each other involve taking a nap (though it might be brief, you might wake up in an entirely different body and need to fetch your working memory from your old body or worse, from RAM).

Or you can repeatedly write your message until you can be sure that no one else wrote over it since you started writing it. And the more threads you have, the more likely another one wrote over your message to the point where all threads are spending all of their time trying to coordinate and no time working.

[–] deleted 2 points 10 months ago (1 children)

Blocking collections?

[–] Buddahriffic 1 points 10 months ago

I'm not familiar with their implementation but they'll likely have one of those mechanisms under the hood.

You can only avoid them in very simple cases that don't really scale up to a large number of threads in most cases. The one exception that does scale well is large amounts of data that can be processed independently of the rest of the data and the results are also independent. 3D rendering is one example, though some effects can create dependencies.

[–] deleted 3 points 10 months ago

So 8 cores is doable but 16 no?