# 12.6. Concise Implementation for Multiple GPUs¶ Open the notebook in Colab Open the notebook in Colab Open the notebook in Colab

Implementing parallelism from scratch for every new model is no fun. Moreover, there is significant benefit in optimizing synchronization tools for high performance. In the following we will show how to do this using high-level APIs of deep learning frameworks. The math and the algorithms are the same as in Section 12.5. Quite unsurprisingly you will need at least two GPUs to run code of this section.

from mxnet import autograd, gluon, init, np, npx
from mxnet.gluon import nn
from d2l import mxnet as d2l

npx.set_np()

import torch
from torch import nn
from d2l import torch as d2l


## 12.6.1. A Toy Network¶

Let us use a slightly more meaningful network than LeNet from Section 12.5 that is still sufficiently easy and quick to train. We pick a ResNet-18 variant [He et al., 2016a]. Since the input images are tiny we modify it slightly. In particular, the difference from Section 7.6 is that we use a smaller convolution kernel, stride, and padding at the beginning. Moreover, we remove the maximum pooling layer.

#@save
def resnet18(num_classes):
"""A slightly modified ResNet-18 model."""
def resnet_block(num_channels, num_residuals, first_block=False):
blk = nn.Sequential()
for i in range(num_residuals):
if i == 0 and not first_block:
num_channels, use_1x1conv=True, strides=2))
else:
return blk

net = nn.Sequential()
# This model uses a smaller convolution kernel, stride, and padding and
# removes the maximum pooling layer
nn.BatchNorm(), nn.Activation('relu'))
resnet_block(128, 2),
resnet_block(256, 2),
resnet_block(512, 2))
return net

#@save
def resnet18(num_classes, in_channels=1):
"""A slightly modified ResNet-18 model."""
def resnet_block(in_channels, out_channels, num_residuals,
first_block=False):
blk = []
for i in range(num_residuals):
if i == 0 and not first_block:
blk.append(d2l.Residual(in_channels, out_channels,
use_1x1conv=True, strides=2))
else:
blk.append(d2l.Residual(out_channels, out_channels))
return nn.Sequential(*blk)

# This model uses a smaller convolution kernel, stride, and padding and
# removes the maximum pooling layer
net = nn.Sequential(
nn.BatchNorm2d(64),
nn.ReLU())
nn.Linear(512, num_classes)))
return net


## 12.6.2. Network Initialization¶

The initialize function allows us to initialize parameters on a device of our choice. For a refresher on initialization methods see Section 4.8. What is particularly convenient is that it also allows us to initialize the network on multiple devices simultaneously. Let us try how this works in practice.

net = resnet18(10)
# Get a list of GPUs
devices = d2l.try_all_gpus()
# Initialize all the parameters of the network
net.initialize(init=init.Normal(sigma=0.01), ctx=devices)


Using the split_and_load function introduced in Section 12.5 we can divide a minibatch of data and copy portions to the list of devices provided by the devices variable. The network instance automatically uses the appropriate GPU to compute the value of the forward propagation. Here we generate 4 observations and split them over the GPUs.

x = np.random.uniform(size=(4, 1, 28, 28))
net(x_shards[0]), net(x_shards[1])

(array([[ 2.2610197e-06,  2.2045990e-06, -5.4046782e-06,  1.2869936e-06,
5.1373163e-06, -3.8297981e-06,  1.4339003e-07,  5.4683455e-06,
-2.8279201e-06, -3.9651122e-06],
[ 2.0698665e-06,  2.0084681e-06, -5.6382510e-06,  1.0498472e-06,
5.5506407e-06, -4.1065477e-06,  6.0829973e-07,  5.4521774e-06,
-3.7365028e-06, -4.1891644e-06]], ctx=gpu(0)),
array([[ 2.4629776e-06,  2.6015521e-06, -5.4362613e-06,  1.2938235e-06,
5.6387894e-06, -4.1360108e-06,  3.5759001e-07,  5.5125247e-06,
-3.1957343e-06, -4.2976326e-06],
[ 1.9431679e-06,  2.2600423e-06, -5.2698210e-06,  1.4807415e-06,
5.4830939e-06, -3.9678889e-06,  7.5751132e-08,  5.6764366e-06,
-3.2530224e-06, -4.0943964e-06]], ctx=gpu(1)))


Once data pass through the network, the corresponding parameters are initialized on the device the data passed through. This means that initialization happens on a per-device basis. Since we picked GPU 0 and GPU 1 for initialization, the network is initialized only there, and not on the CPU. In fact, the parameters do not even exist on the CPU. We can verify this by printing out the parameters and observing any errors that might arise.

weight = net[0].params.get('weight')

try:
weight.data()
except RuntimeError:
print('not initialized on cpu')
weight.data(devices[0])[0], weight.data(devices[1])[0]

not initialized on cpu

(array([[[ 0.01382882, -0.01183044,  0.01417866],
[-0.00319718,  0.00439528,  0.02562625],
[-0.00835081,  0.01387452, -0.01035946]]], ctx=gpu(0)),
array([[[ 0.01382882, -0.01183044,  0.01417866],
[-0.00319718,  0.00439528,  0.02562625],
[-0.00835081,  0.01387452, -0.01035946]]], ctx=gpu(1)))


Next, let us replace the code to evaluate the accuracy by one that works in parallel across multiple devices. This serves as a replacement of the evaluate_accuracy_gpu function from Section 6.6. The main difference is that we split a minibatch before invoking the network. All else is essentially identical.

#@save
def evaluate_accuracy_gpus(net, data_iter, split_f=d2l.split_batch):
"""Compute the accuracy for a model on a dataset using multiple GPUs."""
# Query the list of devices
devices = list(net.collect_params().values())[0].list_ctx()
# No. of correct predictions, no. of predictions
metric = d2l.Accumulator(2)
for features, labels in data_iter:
X_shards, y_shards = split_f(features, labels, devices)
# Run in parallel
pred_shards = [net(X_shard) for X_shard in X_shards]
pred_shard, y_shard in zip(
pred_shards, y_shards)), labels.size)
return metric[0] / metric[1]


We will initialize the network inside the training loop. For a refresher on initialization methods see Section 4.8.

net = resnet18(10)
# Get a list of GPUs
devices = d2l.try_all_gpus()
# We will initialize the network inside the training loop


## 12.6.3. Training¶

As before, the training code needs to perform several basic functions for efficient parallelism:

• Network parameters need to be initialized across all devices.

• While iterating over the dataset minibatches are to be divided across all devices.

• We compute the loss and its gradient in parallel across devices.

• Gradients are aggregated and parameters are updated accordingly.

In the end we compute the accuracy (again in parallel) to report the final performance of the network. The training routine is quite similar to implementations in previous chapters, except that we need to split and aggregate data.

def train(num_gpus, batch_size, lr):
ctx = [d2l.try_gpu(i) for i in range(num_gpus)]
net.initialize(init=init.Normal(sigma=0.01), ctx=ctx, force_reinit=True)
trainer = gluon.Trainer(net.collect_params(), 'sgd',
{'learning_rate': lr})
loss = gluon.loss.SoftmaxCrossEntropyLoss()
timer, num_epochs = d2l.Timer(), 10
animator = d2l.Animator('epoch', 'test acc', xlim=[1, num_epochs])
for epoch in range(num_epochs):
timer.start()
for features, labels in train_iter:
X_shards, y_shards = d2l.split_batch(features, labels, ctx)
ls = [loss(net(X_shard), y_shard) for X_shard, y_shard
in zip(X_shards, y_shards)]
for l in ls:
l.backward()
trainer.step(batch_size)
npx.waitall()
timer.stop()
print(f'test acc: {animator.Y[0][-1]:.2f}, {timer.avg():.1f} sec/epoch '
f'on {str(ctx)}')

def train(net, num_gpus, batch_size, lr):
devices = [d2l.try_gpu(i) for i in range(num_gpus)]
def init_weights(m):
if type(m) in [nn.Linear, nn.Conv2d]:
nn.init.normal_(m.weight, std=0.01)
net.apply(init_weights)
# Set the model on multiple GPUs
net = nn.DataParallel(net, device_ids=devices)
trainer = torch.optim.SGD(net.parameters(), lr)
loss = nn.CrossEntropyLoss()
timer, num_epochs = d2l.Timer(), 10
animator = d2l.Animator('epoch', 'test acc', xlim=[1, num_epochs])
for epoch in range(num_epochs):
net.train()
timer.start()
for X, y in train_iter:
X, y = X.to(devices[0]), y.to(devices[0])
l = loss(net(X), y)
l.backward()
trainer.step()
timer.stop()
print(f'test acc: {animator.Y[0][-1]:.2f}, {timer.avg():.1f} sec/epoch '
f'on {str(devices)}')


Let us see how this works in practice. As a warm-up we train the network on a single GPU.

train(num_gpus=1, batch_size=256, lr=0.1)

test acc: 0.93, 13.5 sec/epoch on [gpu(0)]

train(net, num_gpus=1, batch_size=256, lr=0.1)

test acc: 0.93, 13.9 sec/epoch on [device(type='cuda', index=0)]


Next we use 2 GPUs for training. Compared with LeNet evaluated in Section 12.5, the model for ResNet-18 is considerably more complex. This is where parallelization shows its advantage. The time for computation is meaningfully larger than the time for synchronizing parameters. This improves scalability since the overhead for parallelization is less relevant.

train(num_gpus=2, batch_size=512, lr=0.2)

test acc: 0.92, 6.9 sec/epoch on [gpu(0), gpu(1)]

train(net, num_gpus=2, batch_size=512, lr=0.2)

test acc: 0.65, 8.9 sec/epoch on [device(type='cuda', index=0), device(type='cuda', index=1)]


## 12.6.4. Summary¶

• Gluon provides primitives for model initialization across multiple devices by providing a context list.

• Data are automatically evaluated on the devices where the data can be found.

• Take care to initialize the networks on each device before trying to access the parameters on that device. Otherwise you will encounter an error.

• The optimization algorithms automatically aggregate over multiple GPUs.

## 12.6.5. Exercises¶

1. This section uses ResNet-18. Try different epochs, batch sizes, and learning rates. Use more GPUs for computation. What happens if you try this with 16 GPUs (e.g., on an AWS p2.16xlarge instance)?

2. Sometimes, different devices provide different computing power. We could use the GPUs and the CPU at the same time. How should we divide the work? Is it worth the effort? Why? Why not?

3. What happens if we drop npx.waitall()? How would you modify training such that you have an overlap of up to two steps for parallelism?

Discussions

1. This section uses ResNet-18. Try different epochs, batch sizes, and learning rates. Use more GPUs for computation. What happens if you try this with 16 GPUs (e.g., on an AWS p2.16xlarge instance)?

2. Sometimes, different devices provide different computing power. We could use the GPUs and the CPU at the same time. How should we divide the work? Is it worth the effort? Why? Why not?

Discussions