Earlier quoted context omitted.
Yes! Whenever you spin up one of our AMIs, there is a README that will guide you through a couple of simple examples. We are about to publish performance results on the monster machines in a few days, so watch out for it. Scaling depends on the compute density of the GPU workload, but in general we've seen pretty good results with 1) Deep learning (caffe) scaling to 16 GPUs (near native scaling with local GPUs, espec…
Have you done any molecular dynamics benchmarks? If so, what kind/what system? I'd be very interested to see those. If you haven't, I could probably contribute some strong and weak scaling testcases.
Combine Multiple AWS Instances into a 16-GPU Monster Machine
21–30 of 47 posts
Re: Combine Multiple AWS Instances into a 16-GPU Monster Machine
#22Earlier quoted context omitted.
Have you done any molecular dynamics benchmarks? If so, what kind/what system? I'd be very interested to see those. If you haven't, I could probably contribute some strong and weak scaling testcases.
We've only done cursory evaluation of NAMD scaling. We saw a 7X improvement going from a non-GPU system to remote GPUs located in a different datacenter over shared 10g. We're not sure if that was with a representative dataset (MD is not our skill set), so if you can help us with a case study we'd be excited to work with you. Please do contact me.
Re: Combine Multiple AWS Instances into a 16-GPU Monster Machine
#23Earlier quoted context omitted.
Yes, your app would have to support multiple GPUs. What's done here is remoting CUDA/OpenCL/etc. calls so that remote GPUs can be accessed from a single instance. When performing device/platform enumeration, all GPUs appear to be directly connected to a single instance -- hence no change to the application required.
Sounds like Plan9's concept of "CPU server mounts" has been reborn as "GPU server mounts." Could actually get traction this time, given that existing multi-GPU programs will Just Work.
Re: Combine Multiple AWS Instances into a 16-GPU Monster Machine
#24At first I thought this was the same problem as automatically breaking up apps to run in multiple cpus. This problem has been heavily researched with no success. Is it the fact that GPU code already runs in parallel streams that makes this possible?
Re: Combine Multiple AWS Instances into a 16-GPU Monster Machine
#25I've found amazon GPU instances to be really expensive (even the spot prices have been high recently), especially if you need it for longer runs for deep learning. The other issue is that the additional layers of virtualization create bandwidth overhead issues. I'd like to see something in the cloud thats bare-metal / full access to GPUs (Maybe a good idea to start one). For scaling higher with a very large number of…
Re: Combine Multiple AWS Instances into a 16-GPU Monster Machine
#26I've found amazon GPU instances to be really expensive (even the spot prices have been high recently), especially if you need it for longer runs for deep learning. The other issue is that the additional layers of virtualization create bandwidth overhead issues. I'd like to see something in the cloud thats bare-metal / full access to GPUs (Maybe a good idea to start one). For scaling higher with a very large number of…
Somebody should make a startup that allows people to sell access to their computers by the minute. Like spot instances in the cloud ... in people's basements. The true sharing economy.
Re: Combine Multiple AWS Instances into a 16-GPU Monster Machine
#27I've found amazon GPU instances to be really expensive (even the spot prices have been high recently), especially if you need it for longer runs for deep learning. The other issue is that the additional layers of virtualization create bandwidth overhead issues. I'd like to see something in the cloud thats bare-metal / full access to GPUs (Maybe a good idea to start one). For scaling higher with a very large number of…
Somebody should make a startup that allows people to sell access to their computers by the minute. Like spot instances in the cloud ... in people's basements. The true sharing economy.
Re: Combine Multiple AWS Instances into a 16-GPU Monster Machine
#28I've found amazon GPU instances to be really expensive (even the spot prices have been high recently), especially if you need it for longer runs for deep learning. The other issue is that the additional layers of virtualization create bandwidth overhead issues. I'd like to see something in the cloud thats bare-metal / full access to GPUs (Maybe a good idea to start one). For scaling higher with a very large number of…
The bigger problem we ran into is that AWS instances use a lot of small GPUs, which don't scale well using a lot of deep neural network tools (e.g. theano). It was never really a viable option for us.
Re: Combine Multiple AWS Instances into a 16-GPU Monster Machine
#29Did you guys think about building it further out to provide a GPU load balancer for multiple frontend machines running Cuda / OpenCL?
Re: Combine Multiple AWS Instances into a 16-GPU Monster Machine
#30I've found amazon GPU instances to be really expensive (even the spot prices have been high recently), especially if you need it for longer runs for deep learning. The other issue is that the additional layers of virtualization create bandwidth overhead issues. I'd like to see something in the cloud thats bare-metal / full access to GPUs (Maybe a good idea to start one). For scaling higher with a very large number of…
Somebody should make a startup that allows people to sell access to their computers by the minute. Like spot instances in the cloud ... in people's basements. The true sharing economy.
Something like a combination of Freenet, TOR, BOINC, blockchain etc. technologies, using the current "legacy" internet as a backbone, where anyone can voluntarily offer their computing and storage resources to the network at varying levels of participation.
Say you could offer your laptop as a simple discovery/directory node to simply help others connect and find stuff, and your desktop as either a static-content serving node or as a computation node that can host distributed applications, like SETI@home or web apps like Facebook.
Maybe even reward cryptocurrency to those who offer the most resources.