Live data from Hacker News

Introducing Amazon EC2 P3 Instances

aws.amazon.com

11–20 of 99 posts

Re: Introducing Amazon EC2 P3 Instances

#11
post #8
post #5

An exaflop of mixed-precision compute for $250M over 3 years. That’s ballpark what the HPC community is paying for their exaflop-class machines. You’d still build your own for that money, I think, but it’s an interesting datapoint.

How long if you build it your own incl electricity prices? If margins are similar to other EC2 instances, you'd probably break-even after 6 months or so. Which makes EC2 uneconomical for any lab/company that can utilise the cluster 24/7. Still nice if you quickly need to get some model results though.

Amazon prices are for the pay as you go model. You can shave a significant amount off the price if you know you're going to be running them for 12 months.

Re: Introducing Amazon EC2 P3 Instances

#12
post #9

The P3 instances are the first widely and easily accessible machines that use the NVIDIA Tesla V100 GPUs. These GPUs are straight up scary in terms of firepower. To give an understanding of the speed-up compared to the P2 instances for a research project of mine: + P2 (K80) with single GPU: ~95 seconds per epoch + P3 (V100) with single GPU: ~20 seconds per epoch Admittedly this isn't exactly fair for either GPU - the…

Great write up as usual! Could you elaborate more on the python overhead a bit? We have fp16 support running in dl4j but I don't think we've really done much with volta yet beyond get it working. In practice, (especially when we do multi gpu async back round loading of data) we find gpus being data starved. I would love to compare support for what you're seeing with pytorch.

Re: Introducing Amazon EC2 P3 Instances

#13
post #2

Price: p3.2xlarge - $3/hr, p3.8xlarge - $12/hr, p3.16xlarge - $25/hr These look very good for half precision training

Come on, no one with any sense pays the on demand price for these things. Watch the spots.

Yes, p3.2xlarge in us-east-1b is currently sitting at $0.3204 spot. That's only marginally more than p2.xlarge (at $0.2259 in us-east-1e).

I'm sure this will change with demand, though. :(

Re: Introducing Amazon EC2 P3 Instances

#15
post #9

The P3 instances are the first widely and easily accessible machines that use the NVIDIA Tesla V100 GPUs. These GPUs are straight up scary in terms of firepower. To give an understanding of the speed-up compared to the P2 instances for a research project of mine: + P2 (K80) with single GPU: ~95 seconds per epoch + P3 (V100) with single GPU: ~20 seconds per epoch Admittedly this isn't exactly fair for either GPU - the…

Great write up as usual! Could you elaborate more on the python overhead a bit? We have fp16 support running in dl4j but I don't think we've really done much with volta yet beyond get it working. In practice, (especially when we do multi gpu async back round loading of data) we find gpus being data starved. I would love to compare support for what you're seeing with pytorch.

Honestly, I didn't spend enough time delving in to the Python overhead, especially in terms of the framework. Most of it would be an issue of my own causing however rather than the framework's. The original code I wrote was never written with data loading / saving in mind as the source for speed issues so I avoided what would have been premature optimization at the time.

Some of the slowdowns now just seem silly and aren't even listed in the per epoch timings: PyTorch doesn't have an asynchronous torch.save(). This means that if you save your model after each epoch, and the model save takes a few seconds, you're increasing your per epoch timings 5-10% just by saving the damn thing!

Regarding FP16, PyTorch supports, and there's even a pull request that updates the examples repo with FP16 support for language modeling and ImageNet. It's not likely to be merged as it greatly complicates a codebase that's meant primarily for teaching purposes but it's lovely to look at. I also think many of the FP16 issues will get a general wrapper and they'll become far more agnostic to the end user. For the most part they're all outlined in NVIDIA / Baidu's "Mixed Precision Training" paper. Might be useful for DeepLearning4j to go through the most common heavy throughput use cases and get them running (just as an example of how to work around issues really) if customers were using P100s/V100s?

I'm really interested in exploring the FP16 aspect as the QRNN, especially for single GPU, is sitting at basically 100% utilization, with almost all the time spent on matrix multiplications. FP16 is about the only way to speed it up at that stage. This gets a tad more complicated regardless as the CUDA kernel is not written in FP16 (and is not easy to do so) but even converting FP16->FP32->(QRNN element-wise CUDA kernel)->FP16 ("pseudo" FP16) should still be a crazy speedup. I tested that on the P100 and it took per epoch AWD-QRNN from ~28 seconds to ~18.

- PyTorch async save issue: https://github.com/pytorch/pytorch/issues/1567

- PyTorch FP16 examples pull request: https://github.com/pytorch/examples/pull/203

- "Mixed Precision Training": https://arxiv.org/abs/1710.03740

Re: Introducing Amazon EC2 P3 Instances

#16
post #10

Earlier quoted context omitted.

Come on, no one with any sense pays the on demand price for these things. Watch the spots.

There are enough companies out there with deep pockets that want to do some ML. They'll pay pay those prices, no questions asked.

Per the marketing material it's up to a PFLOP of mixed precision (is that the same as just saying "half precision"? or is it 8 bit?) for $25/hour.

I can easily see people paying full price for that. Still, spot price is currently $2.40.

Re: Introducing Amazon EC2 P3 Instances

#18
Here's my results:

Testing new Tesla V100 on AWS. Fine-tuning VGG on DeepSent dataset for 10 epochs.

GRID 520K (4GB) (baseline):

* 780s/epoch @ minibatch 8 (GPU saturated)

V100(16Gb):

* 30s/epoch @ minibatch 8 (GPU not saturated)

* 6s/epoch @ minibatch 32 (GPU more saturated)

* 6s/epoch @ minibatch 256 (GPU saturated)

Re: Introducing Amazon EC2 P3 Instances

#19

Why Ireland and not the UK? I can imagine a lot of startups/banks in London could use this... Brexit fears?

I wouldn't read too much into this - Amazon's Ireland region was deployed earlier (2008?) than London (2016?) and seems to receive updates earlier too.

Re: Introducing Amazon EC2 P3 Instances

#20

Why Ireland and not the UK? I can imagine a lot of startups/banks in London could use this... Brexit fears?

London only came online relatively recently, maybe there's some operational stuff getting in the way of deploying? Or perhaps London has relatively few users at the moment, so the number of clients who will be able to take advantage of more specialised instances is also relatively low?
Post reply on HN