Jenya

13 posts

Jenya

Jenya

@reducescatter

🧑‍🔧 AI Plumber 🪫 Electronics Tinkerer 🎨 Glitch Art

San Francosco Bay Area Katılım Nisan 2024
38 Takip Edilen36 Takipçiler
Jenya
Jenya@reducescatter·
@rvarm1 I wish you all the best, it was an absolute pleasure working with you 🫡
English
0
0
1
374
Rohan Varma
Rohan Varma@rvarm1·
It’s my last week at Meta this week after an amazing 6 years! I’m grateful for having had the opportunity to contribute to PyTorch both internally and for the community, as well as work on some interesting scaling related problems as part of Llama. Excited for what’s next!
English
16
3
369
68.5K
Jenya
Jenya@reducescatter·
@RhysSullivan This reminds me how they used to have a built-in messenger, I wonder if it would evolve into something like slack and consequently make it easier to have a better surface to integrate copilot.
English
0
0
0
21
Rhys
Rhys@RhysSullivan·
incredible how pretty much the entire github homepage is useless
Rhys tweet media
English
472
864
19.7K
2.9M
Jenya retweetledi
Abhishek Kadian
Abhishek Kadian@abhisk_kadian·
Llama3.2 models are here 🎉! We are releasing the multimodal and lightweight Llama models.
Abhishek Kadian tweet media
English
3
5
16
3.2K
Jenya
Jenya@reducescatter·
This enables the warp scheduler to keep GPUs busy and is a key mechanism that helps to hide latency and it's often preferred to oversubscribe threads to SMs. † Intel's Hyper-Threading similarly enables fast context switches, though.
English
0
0
0
46
Jenya
Jenya@reducescatter·
In contrast †, GPUs can context switch ~instantaneously when a thread executes a high-latency operation like accessing global memory, without requiring more than a few extra cycles.
English
1
0
0
50
Jenya
Jenya@reducescatter·
When optimizing CPU workloads, it's common to avoid context switches due to the overhead of saving and recovering the state of the running thread. In contrast †, GPUs can ... #gpus #ai #ml
English
1
0
2
79
Jenya retweetledi
Vedanuj Goswami
Vedanuj Goswami@vedanujg·
Happy to be part of this incredible journey of Llama3 and to share the best open weight 8B and 70B models! Our largest 400B+ model is still cooking but we are providing a sneak peek into how it is trending! Check more details here ai.meta.com/blog/meta-llam…
English
0
10
44
5K
Jenya
Jenya@reducescatter·
Having a massive fleet of GPUs is only a part of the story, you absolutely need to have an amazing team who can make it work.
English
0
0
3
197
Jenya
Jenya@reducescatter·
@karpathy's insights on the complexities of training LLMs really hit home. Keeping the #llama3 training alive was a journey filled with hard challenges across the entire tech stack. Reading it kept me sane, knowing others have a similar experience.
Andrej Karpathy@karpathy

Nice read on the rarely-discussed-in-the-open difficulties of training LLMs. Mature companies have dedicated teams maintaining the clusters. At scale, clusters leave the realm of engineering and become a lot more biological, hence e.g. teams dedicated to "hardware health". It can be a frustrating daily life experience of training large models to "babysit" the training run. You're there carefully monitoring the vital signs of your run: loss spikes, numerical issues, throughput, gradient norms, policy entropy, etc. Every time the run degrades or flatlines (can happen often), you quickly look for the stack trace to see what's up. You have to do this fast or 10,000 GPUs could be idling. Often, it is a new, exotic, scary-looking error you've never seen before so you summon help to see if anyone can see what's up. The worst ones like to occur at 4am. Often no one can, so you just ban some nodes that look a bit sketchy and try to restart the run. Sometimes the run goes down just because you have not earned the favors of your gods that day, so you put a while True: loop around your launch command. The underlying issues can be highly diverse, from some GPUs just getting a bit too hot and suddenly doing incorrect multiplication once in a while, to some router going down and decreasing the networked file system I/O, to someone in the datacenter physically disconnecting a wire as part of an un-communicated maintenance. Sometimes you'll never know. Another necessary related citation here is the famous OPT-175B logbook and I'd hope more like it can see the light of day in the future. (see chronicles/OPT175B_Logbook.pdf in the git repo) x.com/aiatmeta/statu… TLDR LLM training runs are significant stress-tests of an overall fault tolerance of a large computing system acting as a biological entity. And when you're shopping around for your compute, think about a lot more than just FLOPs and $. Think about the whole service from hardware to software across storage, networking, and compute. And think about whether the team maintaining it looks like The Avengers and whether you could become best friends.

English
1
1
11
4.4K
Jenya
Jenya@reducescatter·
Feeling incredibly grateful for the entire team's dedication and hard work on the release of #Llama V3. It was a journey of long hours and immense effort, but we did it! Excited to finally put this in the hands of our amazing open source community.
English
0
0
6
1K