3 ms·
Yup, stick around for the QA. During the presentation it sounded like it was practically ready. Someone asked about memory locality when actually putting them t
by sidibe 5y ago
Yup, stick around for the QA. During the presentation it sounded like it was practically ready. Someone asked about memory locality when actually putting them together and the infra guy started saying it's a really hard problem. Finally Elon said "This will be ready next year"
The whole presentation (not just dojo) felt like the kind of presentation you give internally to a VP when you haven't been making much progress. Flood them with challenges and implementation detail decisions they can't follow and don't talk about results.
- jeffbee 5y agoOther than being hypothetical vaporware, how is it different from a cabinet full of google TPUs?
- dragontamer 5y ago> The whole presentation felt like the kind of presentation you give internally to a VP when you haven't been making much progress. Flood them with challenges and implementation detail decisions they can't follow and don't talk about results. That hurts me a bit, because I feel like I've done that sometimes. But that's what makes it easy for me to pick up on, when other people do that sort of stuff. Good presentations are more direct. Ex: Here's our ResNet-50 benchmark numbers. Or at very least, "We didn't run ResNet50, because we don't think its realistic. Instead, we ran this other benchmark along with NVidia A100 GPUs and are proving that our system is faster " ---------- You need to prove your system has a benchmark score worth considering before diving into architectural details... at least if you're trying to attract engineering talent to your project.