2,985 karma · joined August 30, 2010
http://lambda.ai | http://www.stephenbalaban.com
Also, because you cited our GPU benchmarks, I also wanted to throw in a mention our GPU instances which have some of the lowest training costs on the Stanford Dawn Benchmarks discussed in the article.
We're looking for a software engineer who wants to write code at our Deep Learning workstation and server company. You will:
* Be responsible for the full stack
* Build reliable, scalable, highly available systems
Required Experience:
* Bachelor's degree in technical field (CS, Physics, EE, Math, etc.)
* Extremely comfortable in a Linux/Unix shell
===
We're located in San Francisco 5 minutes away from the 22nd street Caltrain.
Apply to:
In addition, when you’re first starting off with Deep Learning you should just build a GPU machine under your desk and use that to train. The suggestion in the post to do horizontally scaled distributed training is a great way to horizontally scale your monthly bill too. I’ve seen dozens of people spend $500 on an AWS training experiment only to realize they could have bought a 2nd hand 1080 Ti with that same money and been able to train for the next 2 years.
I'm saying that you are still missing another 8x on the way from 19.5 TFLOPS / GPU to 624 TFLOPS / GPU. 19.5 (base FP32 theoretical peak performance) * 2 (FP16 instead of FP32) * 2 (counting sparse matrix ops as dense ops) * 8 (unknown) = 624 TFLOPS.
The 5 "petaflops" number is a creatively constructed marketing number based on FP16 TensorCore "flops", sparse matrix calculations, and then multiplying by 8x for some reason. They basically take the 19.5 FP32 TFLOPS number and multiply it by 32x to get to the claimed 624 "TFLOPS" for a single A100. 8 * 624 = 5 "petaflops". I see they get 2x by actually using FP16 instead of FP32, 2x from counting sparse matrix ops as dense ops, and 8x from somewhere else that I have no idea.
[1] https://devblogs.nvidia.com/nvidia-ampere-architecture-in-de...
[2] https://www.top500.org/resources/frequently-asked-questions/
We're looking for a software engineer who wants to write code at our Deep Learning workstation and server company. You will:
* Be responsible for the full stack
* Build reliable, scalable, highly available systems
Required Experience:
* Bachelor's degree in technical field (CS, Physics, EE, Math, etc.)
* Extremely comfortable in a Linux/Unix shell
===
We're located in San Francisco 5 minutes away from the 22nd street Caltrain. Right now everything is remote!
Apply to:
We're looking for a software engineer who wants to write code at our Deep Learning workstation and server company. You will:
* Be responsible for the full stack
* Build reliable, scalable, highly available systems
Required Experience:
* Bachelor's degree in technical field (CS, Physics, EE, Math, etc.)
* Extremely comfortable in a Linux/Unix shell
===
We're located in San Francisco 5 minutes away from the 22nd street Caltrain.
Apply to:
We're looking for a software engineer who wants to write code at our Deep Learning workstation and server company. You will:
* Be responsible for the full stack
* Build reliable, scalable, highly available systems
Required Experience:
* Bachelor's degree in technical field (CS, Physics, EE, Math, etc.)
* Extremely comfortable in a Linux/Unix shell
===
We're located in San Francisco 5 minutes away from the 22nd street Caltrain.
Apply to:
- It’s sluggish.
- The password sharing experience sucks.
- The drop down menus often get obfuscated in weird ways.
We're looking for a software engineer who wants to write code at our Deep Learning workstation and server company. You will:
* Be responsible for the full stack
* Build reliable, scalable, highly available systems
Required Experience:
* Bachelor's degree in technical field (CS, Physics, EE, Math, etc.)
* Extremely comfortable in a Linux/Unix shell
===
We're located in San Francisco 5 minutes away from the 22nd street Caltrain.
Apply to: https://lambdalabs.com/careers
It just doesn’t make financial sense to use the big the cloud service providers for those with consistent workloads. I always hear stories where folks have saved hundreds of thousands in infrastructure costs with owning + co-lo.
Seems like it already can dramatically reduce the amount of work involved in making an animation. Very cool to see pixel art animated at 60 FPS!
Not to mention that the text generated by GPT-2 can often fool an online reader whereas HMMs have the problem of being long-term incoherent and don’t reference back to subjects of the sentence like GPT-2 often does.
I’m not staying you should believe the AI hype in news media. But the paper does contain a lot of thorough analysis and comparison to the previous state of the art.
https://cdn.openai.com/better-language-models/language_model...
You also need to take into account the cost of changing and tuning your code to run on a TPU.
There's a reason why that stuff has remained a niche for people interested in trying to implement Vannevar Bush's "As We May Think".
Perceived pace of progress when seen from the inside of a field is significantly slower than the perceived pace of progress from the outside. That said, I will agree that the progress in AI and face recognition since 2011 has been phenomenal.
For example, with CNNs, you are building up feature activation volumes based on the entire previous layer. The edges between layer N only connects to two nodes in layer N-1. What are the nodes even supposed to represent? This is not how CNNs works. This explains nothing and is actually just confusing.
This entire diagram should be re written using the block diagrams from the actual papers.
I know this is unrelated, but I want to thank you for your work on Kessel Run. It’s inspiring to meet folks in the DOD working hard on making software work for our national defense. I ran into some of your colleagues and was very impressed and excited about that program.
https://oklahoman.com/article/2151107/cowboy-hall-figure-die...
https://lambdalabs.com/blog/8-v100-server-on-prem-vs-p3-inst...
And no, AMD doesn't count. ROCm is a mess.