>>55384825 name of the short haired cutie pier? I wanna

>>55384868
Mayli
purest girl youll ever meet :^)))))

>>55384893
>using the smiley with a carat nose

>>55386387
It's because she's done two Facial Abuse videos and he wishes to indicate a sly ruse.

>>55386458
Deviant.

File: pepepepe.gif (2MB, 260x462px) Image search: [Google]

2MB, 260x462px

>>55384825
you can't have a baby in a month by getting nine women pregnant.

>>55384825
Because most programmers are shit

>>55384825
look. some operations cannot be parallelized, exactly like >>55387146 said.
and gpus have so many cores, because each one can work on different environment object.

>>55384825
because designing parallel code is hard.

there are issues with issues with access, races, synchronization. if you don't know exactly what you are doing you don't anything and coders are fucking retarded.

>>55387146
Fucking love this gif

>>55384825
GPUs aren't suitable for most general processing tasks.

>>55388489
What this guy said.

>>55387146
And this is important too and it is pretty much the reason why most non-cpu intensive tasks aren't worth parallelizing. Also parallizing introduces overheads and if the introduced overheads are greater than the speedup then it is not worth doing.

File: 1463933746037.jpg (141KB, 1024x740px) Image search: [Google]

141KB, 1024x740px

>>55388548
>GPUs aren't suitable for most general processing tasks
actually they are. if you have some big chunk of data you need to process you can implement it on gpu for huge profit.

the problem is, you have to implement it. as in, actually design the algorithm yourself, because there's shit all in this field, even in terms of raw whitepapers from some european phd. then you have to know how to insert the gpu part into the big workflow to get your profit.

for people that use c# or python, or even for your regular c++ oop-shitter this is nigh impossible.

>>55386458
thats not her you idiot

>>55388668
You may want to learn what general processing actually means.

>>55387146
please let there be a video where she REEEEEEEEEEEEEEEEEEs with this thing

>>55384825
I don't get paid for that shit desu.

>>55388668
GPUs can only perform a very limited set of tasks and afaik the best way to summarize it is that they can only do the same thing at the same time, but with different data

which is helpful for graphics because you're shading thousands of polygons/triangles per second but not so helpful for general processing where one core might do this and another one something completely different

File: 2008May27194354_3107.jpg (68KB, 537x600px) Image search: [Google]

68KB, 537x600px

>>55384825
they are though

>>55384825
Parallel and concurrent programming is more difficult than pajeets and codemonkies can handle.
There are tools more appropriate than oop but that as well is too difficult for your average programmer.
Instead people jump on node.js etc.

>falling for the Moar core meme
>not realizing that except niche applications like gaming, rendering, or VR an i3 suits most people just fine
>needing tu justify your purchase of Intel core i7 extreme edition

We need more cores. Not just dozens but hundreds of thousands. We need massively parallel processing to be better and more common so we can actually use them for tech that is within reach for consumers.
I'm thinking real time path traced games for example. For that to work in real time you literally just "add moar cores" in essence.

>>55387146
Sauce?

>>55389886
I would love real time raytracing to be possible. It just adds a quality to the images, no matter how simple they are that simply can't be reproduced by all this hacky shit that most game engines implement. Also the simplicity is amazing and calls for extremely specialized hardware.

Anyway, real time raytracing already is possible with current hardware, the problem is that it generates very noisy images, so you would want to lower the resolution to maybe something like 720p. But atm everybody goes apeshit about 2160p gaming which is like 9 times the pixels, so the noise is three times more apparent, which is not wanted.

https://www.youtube.com/watch?v=BpT6MkCeP7Y
This is a video generated in real time by two Titan X. It's super noisy while moving (it integrates successive frames, which is of course not really wanted), but it shows nicely the photorealism that this kind of rendering provides. The noise needs to be lowered, but a little of it actually plays nicely with the photorealistic looks of it (and when you think about it: Photos are noisy as well for the exact same reasons).

>>55390014
>that video
heh, funny, I just had a whole course on advanced graphics, taught by the guy that made Brigade.
He talked quite a lot about his ray/path tracing engines, super fucking interesting.

>>55388668
You really don't have a clue what you are talking about.

Maybe artificial intelligence will fix this problem

>>55389636
yes it is

>>55387146
>you can't have a baby in a month by getting nine women pregnant.

Thank you for explaining this without the use of fucking cows and burgers.

>>55386458
She did mote than one?