It's a micromachines ad from the '80s. He talked like that in all of them!
As for speed, to a computer we don't talk very fast, not even that guy.
I wonder if it could handle Rap God by Eminem....Let's find out!
As for speed, to a computer we don't talk very fast, not even that guy.
I wonder if it could handle Rap God by Eminem....Let's find out!
[00:00.000 --> 00:09.000] Look, I was going to go easy on you, not to hurt your feelings, but I'm only going to get this one chance.
[00:09.000 --> 00:11.000] Something's wrong, I can feel it.
[00:11.000 --> 00:17.000] It's just a feeling I've got, like something's about to happen, but I don't know what.
[00:17.000 --> 00:21.000] If that means what I think it means, we're in trouble, big trouble.
[00:21.000 --> 00:24.000] Had to be as bananas as you say, I'm not taking any chances.
[00:24.000 --> 00:26.000] You're just one to die for.
[00:26.000 --> 00:32.000] I'm beginning to feel like a rap god, rap god. All my people from the front to the back nod, back nod.So...probably?
Pre-post edit: I can't get it to work.
I've installed pytorch with cuda via pip3, installed the nVidia toolkit and it doesn't see it:
>>> import torch >>> torch.cuda.is_available() False
I've wasted like an hour and a half on it now. I'm not a python dev, and don't have any ML experience so this was just for fun and now it's not anymore.
I tried compiling pytorch with vulkan support, but there are a few LDFLAGS that are wrong. I'll try to solve that some time later.
One piece of advice: use distribution packages! Arch provides pytorch-cuda, and has PKGBUILDS as well.
For reproductibility, I wish we were all on Nix/Guix, but that's not the case (and CUDA+HW dependency would make it complicated).
I can't find a source now, but I remember reading some code where the maintainer had to change a huge chunk of code because the point change for a dependency library literally flipped either how the library handled height/width or BGR channels (I can't remember which one but it was preposterous) from the 2.5.4 to the 2.5.5 version. There is no reason for doing that - it breaks everything just for grins and giggles.
Python itself is also a problem, but that's a rant for another day. Ah, how I wish Ruby had become the defacto language of choice for ML/Deep Learning!