Is this correct?
>>51528768
Why aren't programmers sensitive to vegens like myself?
No, not even close.
not really but whatever
try to stop finding an analogy for every aspect of computing, it's a bad habit and most of the time the analogies don't fit particularly well
>>51528782
Because being vegan is a choice you made. Just like I choose to ignore the feelings of vegan people.
Yeah, that's pretty much exactly how it works. It's why AMD's processors are just so good. They have a lot more cores so they're capable of handling a lot more information at once -- often twice as much! It's a little known secret that Intel's marketing team doesn't want you to know.
>>51528822
Being a vegen is like not being a thief or not being a murderer. It's the only rational, morally right thing to do.
Is this supposed to be an explanation of parallel computation?
The 9.6 GHz figure is bullshit, but the general idea of splitting a problem and letting multiple processing cores each do a part of it is legit.
Getting a 4x speedup on 4 cores is the best you can get. You only get a close to perfect scaling speedup if the program can be neatly cut up so each core has to do the same amount of work, when cores don't have to communicate a lot and wait for each other, and when nearly all of the program can be done in parallel.
Holy fuck this is a bad analogy.
1. The chunks are not even. Processes are split up, and if they can't be divided evenly then it takes as long as the longest chunk.
2. Not every individual program has been optimized for multiple cores. Even if they haven't, though, the operating system can divide tasks between cores, just not perform multiple tasks at the same time for the same program.
3. If you didn't understand the only thing that this diagram explains (processes are split up) then you are beyond saving.
Real world modern day parallel computing explained.
>>51529222
someone is hyper threading.
>9.6 GHz
The fuck?
It's not a very good analogy. Finding analogies for everything is just impossible. At some point it makes more sense to stop using analogies and just learn the concepts.
>>51529271
I heard a whoosh noise as you sidestepped around the joke anon.
>>51528768
>>51529222
I don't know whether this analogy is even fundamentally sound, but this is the closest I could make it.
>>51529656
Now the question is do you actually want four burgers right now? If not, your 3 cores are just going to run idle as in >>51529222
>>51529670
i'd take four white castle sliders over a regular burger anytime
>>51529713
lol yeah i should have made the left burger the same size for clarity.
![evangelion1ee[2].jpg](https://i.imgur.com/pecnt9k.jpg "evangelion1ee[2].jpg")
>>51528768
why is the cow already cut in 4 piece?
>>51529656
>implying all the processors can get ahold of the buns and vegetables at the same time
>>51528768
wrong
get a xeon
>>51529740
Atleast they got Shinji's monkey ears down
>>51528851
There's nothing rational about pathological altruism.
>>51529656
>8 seconds
What's with you people? Turning a single threaded app into a multithreaded one makes it run faster. Albeit not at the ideal presented in the OP.
>>51530216
Many common tasks are not obviously threadable at all. It's still a rough programming challenge.
Besides, you wouldn't get 4 times the output along with 4 times the speed - it would be one or the other.
>>51528768
More or less, sure. But the cow has to be made as four pieces by the programmer.
If it's not, then you end up shoving a whole cow through a quarter of the grinder.
My experience with this comes almost entirely from Dwarf Fortress.
>>51529740
The most pointless show, IN THE WORLD.
>>51529222
Underrated analogy
>>51529740
those are called threads, retard
Does anyone have the nividia version where the cow gets turned into a burnt burger
>>51529222
Literally this. Hey programmers of the world, realize that this is the biggest bottleneck in computing and you can't keep on expecting the EE guys to make up for your shortcomings forever.
>>51530676
In an ideal world.
This is 99% true for tasks like video encoding or ray tracing. Not true for lots of other common tasks.
Just don't forget that you can't make a single cow N times faster by having more of them mating.
Though this hardly matters when only crunching burger meat. Or numbers.
>>51530676
Wouldn't each core take 2 seconds though? The entire point is that they're doing the work at the same time. One 2.4GHz core on a quad-core CPU isn't going to do the work faster than a 2.4GHz core on any other core-count CPU.
>>51530668
There's always the alternative.
>>51528768
The way I explained it to my dad isn't accurate, but it did help him understand it because he knows cars.
Think of the CPU cores as cylinders in an engine. You really could get by on a single cylinder, but it would be loud, large, hard to change speed and not very smooth compared to your multi-cylinder engines.
>>51530962
lol'd
>>51529335
9.6 = 2.4*4
I can't believe how young you guys are holy shit...
>>51528847
>>51531114
Pretty sure the guy you responded to understood multiplication. lol.
