Vidnexa Skip to main content
Create Account
VidNexa
Up next
 
00:00 / 00:00
QualityAutochevron_right
Playback speedchevron_right
Audio trackchevron_right
Chapterschevron_right
Autoplay On
Loop Off
Sticky player Off
Sleep timerOffchevron_right
Subtitles/CC On
Captionschevron_right
Keyboard shortcuts ?
Stats for nerds
Sleep timer ended
⏪ 10s
⏩ 10s

Per-Layer Embeddings (PLE) in Gemma 4 explained

9.6K views • 1 month ago
Watch Party
5 Comments
@sebuzdugan
@@sebuzdugan1 month ago
the red flag is that unchanged active parameters says nothing about memory bandwidth, and ple may still make inference slower on real hardware
@gvi341984
@@gvi3419841 month ago
Rate Google is moving it's going to be agent size
@Mrlogic-i8w
@@Mrlogic-i8w1 month ago
What strikes me most here is not the 2.3B table, but the move from dense compute to sparse retrieval. Does PLE make the model smarter, or just cheaper to run?
@JayRevonoJMCGNC
😮😮😮😮😮😮Wow Youtube Team and Google Team this actually Good with 😊
@masoudmaani
@@masoudmaani1 month ago
that&#39;s why the 4bit quantize of this model is larger than a 8bit quantize of a llama style architecture. <br>which is ridiculous design for a supposedly edge model.<br>in fact, let me tell you exactly how ridiculous it is, at 4bit gemma 12b which is a dense model, is smaller than the 4bit quant of E2B which is only 4b total. 3x more parameters, about 800mbs smaller. (using bnb linear quant)<br>my real question is, none of you geniuses had a calculator to just roughly calculate these numbers?