Media is so focused on CPUs, they are missing the fact that Apple focused on the GPU and Neural Engine for this round of chips
GPU advancements in M3 and A17 Pro [video]
101–110 of 148 posts
Re: GPU advancements in M3 and A17 Pro [video]
#102Media is so focused on CPUs, they are missing the fact that Apple focused on the GPU and Neural Engine for this round of chips
It was wild seeing Linus Tech Tips demoing resident evil village on the iPhone 15 Pro.
Re: GPU advancements in M3 and A17 Pro [video]
#103I’m always impressed with the speech synthesis that Apple uses to make the voiceovers in these videos. Some of them almost sound like real people!
The guy introduced himself by name, I was really confused for a while if it was just a human trained to sound like an AI, or an AI trained to sound like a human.
Perhaps they ask the AI speech/content generator to give itself a name as part of its training prompt.
Re: GPU advancements in M3 and A17 Pro [video]
#104Does M3 still outputs garbage which make external displays flicker? https://forums.macrumors.com/threads/m1-m2-flickering-ghosti... https://www.benq.com/en-us/knowledge-center/knowledge/how-to... https://www.howtogeek.com/805459/mac-flickering-external-scr...
This issue can be fixed by switching the display to RGB [1]. So I think it’s a software bug but it‘s really annoying since the fix sometimes resets and the bug only occurs when there is a lot of black on the screen.
[1] https://gist.github.com/GetVladimir/c89a26df1806001543bef4c8...
Re: GPU advancements in M3 and A17 Pro [video]
#105Earlier quoted context omitted.
you could never hear the audio that cleanly on a VHS even with HiFi tracks.
It is about attitude in voice, not about audio quality. It is very noticeable at 1.5x speed, 1x speed is too slow anyway with infinite pauses for such low density technical details.
It’s an engineer and they provide a transcription.
Re: GPU advancements in M3 and A17 Pro [video]
#106Earlier quoted context omitted.
Question from a GPU novice. I presume a thread is the individual calculation perform on one element of the vector? Can the 128 cores, or 20 SM perform different operations at the same time or all 24,576 threads perform the same operation at the same time, on a vector of data of length of 24,576?
"128 * the-number-of-cores" of threads can make progress truly in parallel (at the same time). 24,576 threads (or however many, I didn't validate the number and it depends on the occupancy, which depends on thread resource usage, like registers => depends on the shader program code) is how many threads can be executed concurrently (as opposed to in parallel), as in, how many of them can simultaneously reside on the G…
So, in NVIDIA parlance, my Skylake laptop would have 128 "cuda cores"?
128 = 4 (physical cores) * 2 (hyperthreading) * 8 (AVX2 f32 lanes) * 2 (floating point ports per core)
Re: GPU advancements in M3 and A17 Pro [video]
#107I’m always impressed with the speech synthesis that Apple uses to make the voiceovers in these videos. Some of them almost sound like real people!
They even created a Twitter profile for this AI persona
Re: GPU advancements in M3 and A17 Pro [video]
#108Earlier quoted context omitted.
"128 * the-number-of-cores" of threads can make progress truly in parallel (at the same time). 24,576 threads (or however many, I didn't validate the number and it depends on the occupancy, which depends on thread resource usage, like registers => depends on the shader program code) is how many threads can be executed concurrently (as opposed to in parallel), as in, how many of them can simultaneously reside on the G…
So, in NVIDIA parlance, my Skylake laptop would have 128 "cuda cores"? 128 = 4 (physical cores) * 2 (hyperthreading) * 8 (AVX2 f32 lanes) * 2 (floating point ports per core)
Sorta, yeah!
Also, your "128 cuda cores" of Skylake variety run at higher frequencies and work off of much bigger caches, so they are faster (in serial manner)...
...until they are slower, because GPU's latency hiding mechanism (with occupancy) hides load latencies very well, while CPU just stalls the pipeline on every cache miss for ungodly amounts of time...
...until they are faster again when the shader program uses a lot of registers and GPU occupancy drops to the floor and latency hiding stops hiding that well.
But core counts - yes, more or less.
Re: GPU advancements in M3 and A17 Pro [video]
#109Does M3 still outputs garbage which make external displays flicker? https://forums.macrumors.com/threads/m1-m2-flickering-ghosti... https://www.benq.com/en-us/knowledge-center/knowledge/how-to... https://www.howtogeek.com/805459/mac-flickering-external-scr...
This issue can be fixed by switching the display to RGB [1]. So I think it’s a software bug but it‘s really annoying since the fix sometimes resets and the bug only occurs when there is a lot of black on the screen. [1] https://gist.github.com/GetVladimir/c89a26df1806001543bef4c8...
I have two monitors connected to M1 mac.
One works perfectly fine and is automatically RGB. Other flickers and when changing to RGB mode it is lime green.
Wonder why it is not problem with Intel Macs and if M3 fixes those bugs?
Maybe it is Apples feature to sell more of their own monitors.
They make sure other high end brands do not work with macOS.
It does not make sense that this kind of bug is 3 years active.
Re: GPU advancements in M3 and A17 Pro [video]
#110Earlier quoted context omitted.
This issue can be fixed by switching the display to RGB [1]. So I think it’s a software bug but it‘s really annoying since the fix sometimes resets and the bug only occurs when there is a lot of black on the screen. [1] https://gist.github.com/GetVladimir/c89a26df1806001543bef4c8...
I have two monitors connected to M1 mac. One works perfectly fine and is automatically RGB. Other flickers and when changing to RGB mode it is lime green. Wonder why it is not problem with Intel Macs and if M3 fixes those bugs? Maybe it is Apples feature to sell more of their own monitors. They make sure other high end brands do not work with macOS. It does not make sense that this kind of bug is 3 years active.
> Wonder why it is not problem with Intel Macs and if M3 fixes those bugs?
Let’s guess: maybe they have different drivers? Would be far from surprising, given that they’re running on different processors.