Azure Disk Storage - Simply Explained

1
00:00:00,000 --> 00:00:04,320
Today's topic is one that almost everyone has heard of, but most people don't fully understand,

2
00:00:04,320 --> 00:00:08,880
as your disk storage, it's the virtual hard drive for your cloud VMs and here's the thing,

3
00:00:08,880 --> 00:00:14,160
every single VM you create needs storage. Pick the wrong type and you're either paying way too much,

4
00:00:14,160 --> 00:00:18,480
or getting terrible performance. By the end of this episode, you'll know the four main disc types

5
00:00:18,480 --> 00:00:22,640
and exactly when to use each one. Grab your coffee and let's dive in.

6
00:00:22,640 --> 00:00:27,560
Why disk type matters? Speed, capacity and cost. So why does disk type even matter?

7
00:00:27,560 --> 00:00:33,560
Three factors determine performance. I/OPS, throughput and latency. I/OPS stands for input,

8
00:00:33,560 --> 00:00:38,760
output operations per second. Basically how many read or write operations the disk can handle at once.

9
00:00:38,760 --> 00:00:42,040
throughput is the data transfer speed measured in megabytes per second.

10
00:00:42,040 --> 00:00:46,280
Latency is the delay. How long that first byte takes to arrive after you ask for it?

11
00:00:46,280 --> 00:00:49,720
Think of it like vehicles. As the Dan handles daily errands just fine,

12
00:00:49,720 --> 00:00:53,400
a pickup truck holds heavier loads and a race car is built for pure speed.

13
00:00:53,400 --> 00:00:57,000
Different disk types follow the same pattern. Standard SSD is your sedan.

14
00:00:57,000 --> 00:01:01,640
Premium SSD is the work truck. Premium SSD V2 is a sports car you can tune yourself.

15
00:01:01,640 --> 00:01:06,120
And ultra-disc is a Formula 1 race car. Here's the trade-off, higher performance costs more money.

16
00:01:06,120 --> 00:01:09,480
The trick is matching the disk to what your workload actually needs,

17
00:01:09,480 --> 00:01:11,960
so you're not over-provisioning and wasting cash,

18
00:01:11,960 --> 00:01:14,360
nor under-provisioning and getting slow performance.

19
00:01:14,360 --> 00:01:17,880
So let's start with the two broad categories of disks you'll attach to a VM.

20
00:01:17,880 --> 00:01:22,520
OSDisk versus DataDisk, the two flavors. When you create a VM in Azure,

21
00:01:22,520 --> 00:01:26,920
it automatically creates an OSDisk. That disk holds the operating system, Windows or Linux,

22
00:01:26,920 --> 00:01:31,000
and it's where the VM boots from. The OSDisk maxes out at four terabytes,

23
00:01:31,000 --> 00:01:34,680
which is more than enough for the OS itself and maybe a few basic applications.

24
00:01:34,680 --> 00:01:38,360
But here's the thing, you can also add DataDisk. These are optional,

25
00:01:38,360 --> 00:01:42,840
and you attach them separately for things like applications, databases, or file storage.

26
00:01:42,840 --> 00:01:45,640
Each DataDisk can go up to 64 terabytes,

27
00:01:45,640 --> 00:01:48,440
and you can attach multiple disks to a single VM.

28
00:01:48,440 --> 00:01:50,440
Need more storage? Just add another disk.

29
00:01:50,440 --> 00:01:55,080
Now both OSDisk and DataDisk use the same four performance tiers.

30
00:01:55,080 --> 00:01:59,640
Standard SSD, premium SSD, premium SSD V2 and ultra-disk.

31
00:01:59,640 --> 00:02:02,040
The difference isn't about speed, it's about purpose.

32
00:02:02,040 --> 00:02:05,720
An OSDisk runs the operating system, a DataDisk runs your applications,

33
00:02:05,720 --> 00:02:08,200
but they both rely on the same underlying disk types.

34
00:02:08,200 --> 00:02:10,680
One more thing, as your disk storage is persistent,

35
00:02:10,680 --> 00:02:14,120
that means your data stays put even when the VM is stopped or restarted,

36
00:02:14,120 --> 00:02:16,360
nothing gets lost when you shut down for the night.

37
00:02:16,360 --> 00:02:19,320
Let's dive into the four tiers, starting with the most affordable.

38
00:02:19,320 --> 00:02:22,600
Standard SSD, the budget workhorse.

39
00:02:22,600 --> 00:02:25,720
Let's start with the entry-level option, Standard SSD.

40
00:02:25,720 --> 00:02:28,440
This is the lowest cost per gigabyte among the SSD tiers,

41
00:02:28,440 --> 00:02:30,760
and it gives you decent performance for basic workloads.

42
00:02:30,760 --> 00:02:33,640
We're talking about a maximum of around 6000 IOPS,

43
00:02:33,640 --> 00:02:36,120
and throughput up to 600 megabytes per second,

44
00:02:36,120 --> 00:02:38,040
depending on the disk size you choose.

45
00:02:38,040 --> 00:02:39,000
So when would you use it?

46
00:02:39,000 --> 00:02:42,760
Think development and test environments where you're spinning up VMs to experiment.

47
00:02:42,760 --> 00:02:44,680
Web servers that don't get heavy traffic,

48
00:02:44,680 --> 00:02:48,040
low traffic applications where a few seconds of delay isn't a big deal.

49
00:02:48,040 --> 00:02:49,720
Remember the vehicle analogy from earlier?

50
00:02:49,720 --> 00:02:51,560
Standard SSD is your reliable sedan.

51
00:02:51,560 --> 00:02:53,160
It gets you to the grocery store and back.

52
00:02:53,160 --> 00:02:55,080
It handles the daily commute just fine,

53
00:02:55,080 --> 00:02:58,440
but you wouldn't use it to hold a trailer full of lumber or race on a track.

54
00:02:58,440 --> 00:03:01,160
It's built for everyday tasks, not heavy lifting.

55
00:03:01,160 --> 00:03:03,160
And here's where you need to be honest with yourself.

56
00:03:03,160 --> 00:03:05,400
If you're running any kind of production database,

57
00:03:05,400 --> 00:03:09,160
SQL server, Oracle, MySQL, skip standard SSD.

58
00:03:09,160 --> 00:03:11,080
Same goes for anything sensitive to latency,

59
00:03:11,080 --> 00:03:12,680
like real-time applications,

60
00:03:12,680 --> 00:03:15,240
or anything that needs a ton of IO operations per second.

61
00:03:15,240 --> 00:03:17,160
Standard SSD just isn't built for that.

62
00:03:17,160 --> 00:03:19,960
For those scenarios, you need a step-up, premium SSD.

63
00:03:20,760 --> 00:03:23,240
Premium SSD, the reliable pro.

64
00:03:23,240 --> 00:03:26,360
Premium SSD handles production workloads without breaking a sweat.

65
00:03:26,360 --> 00:03:30,200
You get consistent low latency and much higher IO apps than standard SSD.

66
00:03:30,200 --> 00:03:32,600
This is where real performance starts showing up.

67
00:03:32,600 --> 00:03:33,960
Here's the simple breakdown.

68
00:03:33,960 --> 00:03:37,240
With premium SSD, performance is directly tied to the disk size.

69
00:03:37,240 --> 00:03:39,960
Pick a disk size and that determines how many IO apps you unlock.

70
00:03:39,960 --> 00:03:42,680
A P30 at one terabyte gives you 5,000 IOPS.

71
00:03:42,680 --> 00:03:45,800
A P60 at four terabytes delivers 20,000 IOPS.

72
00:03:45,800 --> 00:03:47,480
Bigger disk means more performance.

73
00:03:47,480 --> 00:03:48,760
So when should you reach for it?

74
00:03:48,760 --> 00:03:51,720
Enterprise applications that need reliable performance.

75
00:03:51,720 --> 00:03:54,360
SQL server databases that aren't massive,

76
00:03:54,360 --> 00:03:56,600
but still demand consistent response times.

77
00:03:56,600 --> 00:03:59,000
Virtual desktops where users expect instant feedback.

78
00:03:59,000 --> 00:04:00,680
Premium SSD handles all of that.

79
00:04:00,680 --> 00:04:01,720
But here's the limitation.

80
00:04:01,720 --> 00:04:03,960
Because performance is locked to disk size,

81
00:04:03,960 --> 00:04:05,720
you're stuck in fixed tiers.

82
00:04:05,720 --> 00:04:07,960
One more IOPS, you have to buy a bigger disk.

83
00:04:07,960 --> 00:04:10,200
Even if you don't need the extra storage space,

84
00:04:10,200 --> 00:04:11,880
that leads to over-provisioning.

85
00:04:11,880 --> 00:04:13,800
Paying for capacity you never use,

86
00:04:13,800 --> 00:04:15,880
just to get the performance you actually need.

87
00:04:15,880 --> 00:04:17,560
Think of it like a dependable work truck.

88
00:04:17,560 --> 00:04:20,040
It's reliable, it's proven, and it gets the job done.

89
00:04:20,040 --> 00:04:22,120
But you're paying for the whole truck even if you only need

90
00:04:22,120 --> 00:04:24,040
the extra payload capacity once a month.

91
00:04:24,040 --> 00:04:27,320
You can't just rent the truck bed for a day and leave the cab parked.

92
00:04:27,320 --> 00:04:31,080
That exact problem is what premium SSD V2 was built to solve.

93
00:04:31,080 --> 00:04:34,440
Premium SSD V2, the flexible performer.

94
00:04:34,440 --> 00:04:36,200
Now, this is where things get interesting.

95
00:04:36,200 --> 00:04:40,200
Premium SSD V2 fixes the big issue with regular premium SSD,

96
00:04:40,200 --> 00:04:43,160
being forced to buy more capacity just to get more performance.

97
00:04:43,160 --> 00:04:46,440
With premium SSD V2, you can independently adjust capacity,

98
00:04:46,440 --> 00:04:48,040
IOPS and throughput.

99
00:04:48,040 --> 00:04:51,640
No downtime, no disk swaps, just change the settings and it happens.

100
00:04:51,640 --> 00:04:54,280
The baseline is generous, you get 3,000 IOPS

101
00:04:54,280 --> 00:04:59,080
and 125 MB/s of throughput included at no extra charge.

102
00:04:59,080 --> 00:05:02,120
That's already more than some standard SSD disks can max out at.

103
00:05:02,120 --> 00:05:06,360
From there you can scale up to 80,000 IOPS and 1,200 MB/s.

104
00:05:06,360 --> 00:05:08,920
Plenty for most general purpose enterprise workloads.

105
00:05:08,920 --> 00:05:12,120
Capacity ranges from one GB/bite up to 64 TB/bites,

106
00:05:12,120 --> 00:05:16,200
whether you need a tiny disk for a lightweight app or a massive one for a data warehouse,

107
00:05:16,200 --> 00:05:20,360
premium SSD V2 covers it and the latency sub-mily second.

108
00:05:20,360 --> 00:05:22,760
For many workloads it's comparable to ultra-disk.

109
00:05:22,760 --> 00:05:25,160
Without the ultra-price tag, here's the real value.

110
00:05:25,160 --> 00:05:30,040
Premium SSD V2 is significantly cheaper than ultra-disk for similar performance levels.

111
00:05:30,040 --> 00:05:31,720
You're not paying a premium for the name.

112
00:05:31,720 --> 00:05:33,320
You're paying for exactly what you need.

113
00:05:33,320 --> 00:05:35,240
Need high IOPS but not massive throughput?

114
00:05:35,240 --> 00:05:38,200
Tune it that way, need lots of throughput but modest IOPS?

115
00:05:38,200 --> 00:05:41,480
Tune it the other way, no one size fits all package forced on you.

116
00:05:41,480 --> 00:05:42,520
So what's it best for?

117
00:05:42,520 --> 00:05:44,200
Mainstream production databases,

118
00:05:44,200 --> 00:05:48,440
line of business applications, any workload that needs high performance but doesn't need ultra-disk

119
00:05:48,440 --> 00:05:49,080
ceiling.

120
00:05:49,080 --> 00:05:52,920
Suicosurver Oracle MongoDB Cassandra, the databases that power real businesses,

121
00:05:52,920 --> 00:05:56,280
premium SSD V2 handles them all, one limitation worth noting.

122
00:05:56,280 --> 00:06:00,840
Premium SSD V2 is currently only available with locally redundant storage or LRS.

123
00:06:00,840 --> 00:06:04,280
That means your data is replicated three times inside a single data center.

124
00:06:04,280 --> 00:06:06,920
It doesn't support zone redundant storage yet,

125
00:06:06,920 --> 00:06:11,240
so if you need your data spread across multiple availability zones for higher resilience,

126
00:06:11,240 --> 00:06:14,520
you'll need other options or add application level redundancy.

127
00:06:14,520 --> 00:06:18,520
Still for most scenarios premium SSD V2 is the sweet spot.

128
00:06:18,520 --> 00:06:20,840
You get the flexibility to right size storage,

129
00:06:20,840 --> 00:06:23,080
the performance to handle serious workloads,

130
00:06:23,080 --> 00:06:26,520
and a cost structure that doesn't punish you for wanting better IOPS.

131
00:06:26,520 --> 00:06:29,560
But if your workload demands the absolute highest performance,

132
00:06:29,560 --> 00:06:33,080
think SEPHANA electronic health records, or real-time trading.

133
00:06:33,080 --> 00:06:34,840
There's one more tier to cover.

134
00:06:34,840 --> 00:06:36,520
Ultra-disk, the supercar.

135
00:06:36,520 --> 00:06:37,800
Now let's talk about ultra-disk.

136
00:06:37,800 --> 00:06:41,960
This is the top tier. We're talking up to 400,000 IOPS per disk,

137
00:06:41,960 --> 00:06:44,120
10,000 megabytes per second of throughput,

138
00:06:44,120 --> 00:06:47,000
and latency measured in microseconds, not milliseconds.

139
00:06:47,000 --> 00:06:51,320
Microseconds, ultra-disk is built for critical workloads where you can't afford downtime.

140
00:06:51,320 --> 00:06:55,160
Apps that need to be fast, massive in-memory databases like SEPHANA,

141
00:06:55,160 --> 00:06:58,040
health record systems where doctors need info instantly,

142
00:06:58,040 --> 00:07:01,160
high frequency trading platforms where microseconds cost millions,

143
00:07:01,160 --> 00:07:04,360
AI and machine learning jobs that crunch huge data sets.

144
00:07:04,360 --> 00:07:05,560
Pricing is different too.

145
00:07:05,560 --> 00:07:07,320
Performance and capacity are separate.

146
00:07:07,320 --> 00:07:11,080
You pick your IOPS and throughput and pay for them separately from storage.

147
00:07:11,080 --> 00:07:14,760
So you can have a small disk with huge speed or a big disk with modest speed.

148
00:07:14,760 --> 00:07:17,080
You don't have to buy extra capacity just to get the IOPS.

149
00:07:17,080 --> 00:07:18,920
There's also a zone redundant storage.

150
00:07:18,920 --> 00:07:21,960
There are as copies your data across three zones in the same region.

151
00:07:21,960 --> 00:07:24,360
So if one data center goes down, your disk keeps working.

152
00:07:24,360 --> 00:07:27,080
That's important for the workloads ultra-disk handles.

153
00:07:27,080 --> 00:07:28,440
Now here's a newer feature.

154
00:07:28,440 --> 00:07:30,280
Instant access snapshots.

155
00:07:30,280 --> 00:07:33,400
It's in preview for ultra-disk and premium SSDV2.

156
00:07:33,400 --> 00:07:37,240
Normally, creating a disk from a snapshot takes time while data rehydrates.

157
00:07:37,240 --> 00:07:40,840
With instant access, you can create a disk in seconds instead of hours.

158
00:07:40,840 --> 00:07:43,800
And the new disk has near full performance right away.

159
00:07:43,800 --> 00:07:45,560
For disaster recovery, that's a big deal.

160
00:07:45,560 --> 00:07:48,280
You can spin up a full copy of your database in minutes.

161
00:07:48,280 --> 00:07:50,280
Think of ultra-disk like a Formula One racecar,

162
00:07:50,280 --> 00:07:52,920
incredible speed, every millisecond counts.

163
00:07:52,920 --> 00:07:55,880
But you don't drive a Formula One car to pick up groceries.

164
00:07:55,880 --> 00:07:59,160
It's built for one thing, going as fast as physically possible.

165
00:07:59,160 --> 00:08:00,120
And you pay for that speed.

166
00:08:00,120 --> 00:08:01,160
So when shouldn't you use it?

167
00:08:01,160 --> 00:08:03,400
For most workloads, ultra-disk is overkill.

168
00:08:03,400 --> 00:08:07,320
Premium SSDV2 covers 95% of cases for a lot less money.

169
00:08:07,320 --> 00:08:10,760
If you're not running SAP HANA or a trading platform or something extreme,

170
00:08:10,760 --> 00:08:12,600
you don't need ultra-disk.

171
00:08:12,600 --> 00:08:16,520
Start with premium SSDV2 only move to ultra if your monitoring shows you need it.

172
00:08:16,520 --> 00:08:17,800
So we've covered the four tiers.

173
00:08:17,800 --> 00:08:19,160
How do you actually choose?

174
00:08:19,160 --> 00:08:20,520
How to choose the right disk?

175
00:08:20,520 --> 00:08:21,880
So you've got the four tiers.

176
00:08:21,880 --> 00:08:22,760
Now how do you pick?

177
00:08:22,760 --> 00:08:23,960
Start with three questions.

178
00:08:23,960 --> 00:08:25,640
First, is it production or dev test?

179
00:08:25,640 --> 00:08:28,200
If it's dev test or a low traffic web server,

180
00:08:28,200 --> 00:08:29,960
standard SSD is all you need.

181
00:08:29,960 --> 00:08:30,680
Don't overthink it.

182
00:08:30,680 --> 00:08:32,760
It saves money and gives good performance.

183
00:08:32,760 --> 00:08:34,920
Second, what IOPS and latency do you need?

184
00:08:34,920 --> 00:08:38,440
If you need low latency and thousands of IOPS, you need premium.

185
00:08:38,440 --> 00:08:39,880
The question is which premium tier?

186
00:08:39,880 --> 00:08:42,360
If your workload is steady regular premium SSD works,

187
00:08:42,360 --> 00:08:45,400
if you want flexibility to adjust performance without swapping disks,

188
00:08:45,400 --> 00:08:47,400
go premium SSDV2.

189
00:08:47,400 --> 00:08:48,440
Third, what's your budget?

190
00:08:48,440 --> 00:08:49,480
This is where it gets real.

191
00:08:49,480 --> 00:08:53,480
Premium SSDV2 is cheaper than ultra for similar performance in most cases.

192
00:08:53,480 --> 00:08:56,040
But if you're running SAP HANA or a trading system,

193
00:08:56,040 --> 00:08:57,640
speed matters more than cost.

194
00:08:57,640 --> 00:08:59,000
Let me give you a quick guide.

195
00:08:59,000 --> 00:09:02,120
Dev test and web servers, standard SSD.

196
00:09:02,120 --> 00:09:03,720
Production with moderate IOPS?

197
00:09:03,720 --> 00:09:04,760
Premium SSD.

198
00:09:04,760 --> 00:09:07,240
Production with high IOPS where you want flexibility.

199
00:09:07,240 --> 00:09:09,000
Premium SSDV2.

200
00:09:09,000 --> 00:09:12,120
Extreme IOPS where sub millisecond latency is critical.

201
00:09:12,120 --> 00:09:12,840
Ultra disk.

202
00:09:12,840 --> 00:09:15,880
Here are some cost optimization tips that actually save money.

203
00:09:15,880 --> 00:09:17,400
Write size your disk from the start.

204
00:09:17,400 --> 00:09:20,520
Don't buy a 40 by premium SSD if you only need 500GB.

205
00:09:20,520 --> 00:09:23,320
Use premium SSDV2 instead of ultra when you can.

206
00:09:23,320 --> 00:09:25,320
It covers most cases for less money.

207
00:09:25,320 --> 00:09:26,520
Clean up old snapshots.

208
00:09:26,520 --> 00:09:28,040
They stack up and cost you.

209
00:09:28,040 --> 00:09:31,240
And choose LRS over ZRS if you don't need zone redundancy.

210
00:09:31,240 --> 00:09:35,560
LRS is cheaper and still gives three copies within one data center.

211
00:09:35,560 --> 00:09:37,960
One thing you don't need to worry about is encryption.

212
00:09:37,960 --> 00:09:41,000
ServerSide encryption with 256-bit AES is always on.

213
00:09:41,000 --> 00:09:42,680
It's FIPS 142 compliant.

214
00:09:42,680 --> 00:09:44,360
Nothing to enable, nothing to configure.

215
00:09:44,360 --> 00:09:46,200
Your data is encrypted addressed by default.

216
00:09:46,200 --> 00:09:49,000
If you need more control, you can use customer managed keys.

217
00:09:49,000 --> 00:09:51,640
But for most scenarios, the default encryption is enough.

218
00:09:51,640 --> 00:09:53,960
Before we wrap up, let's touch on a couple more features

219
00:09:53,960 --> 00:09:56,040
that matter for durability and security.

220
00:09:56,040 --> 00:09:59,400
Security, durability and snapshots.

221
00:09:59,400 --> 00:10:03,880
As your disk storage targets 99.9% availability thus that's 5.9s.

222
00:10:03,880 --> 00:10:05,080
How do they pull that off?

223
00:10:05,080 --> 00:10:05,720
Simple.

224
00:10:05,720 --> 00:10:07,160
Three copies of every piece of data.

225
00:10:07,160 --> 00:10:11,560
With locally redundant storage, those three copies stay inside one data center.

226
00:10:11,560 --> 00:10:12,520
A disk fails.

227
00:10:12,520 --> 00:10:14,600
Another copy takes over instantly.

228
00:10:14,600 --> 00:10:18,920
With zone redundant storage, copies spread across three availability zones in the same region.

229
00:10:18,920 --> 00:10:20,600
An entire data center goes dark.

230
00:10:20,600 --> 00:10:22,360
Your data stays safe encryption.

231
00:10:22,360 --> 00:10:23,480
Always on by default.

232
00:10:23,480 --> 00:10:28,680
ServerSide encryption uses 256-bit AES and meets FIPS 142 standards.

233
00:10:28,680 --> 00:10:30,200
That covers data addressed.

234
00:10:30,200 --> 00:10:31,880
But maybe you need more control.

235
00:10:31,880 --> 00:10:35,080
Customer managed keys let you hold the encryption keys yourself.

236
00:10:35,080 --> 00:10:36,840
Encryption at host goes further.

237
00:10:36,840 --> 00:10:38,920
It covers temp disks and disk caches,

238
00:10:38,920 --> 00:10:40,920
which the default encryption leaves out.

239
00:10:40,920 --> 00:10:43,240
For truly sensitive workloads, you can stack both.

240
00:10:43,240 --> 00:10:45,160
Snapshots are point in time backups.

241
00:10:45,160 --> 00:10:47,160
They run without slowing your disk down.

242
00:10:47,160 --> 00:10:52,120
The new instant access, snapshots for ultra-disk and premium SSD V2

243
00:10:52,120 --> 00:10:53,720
change the game entirely.

244
00:10:53,720 --> 00:10:57,560
You can create a disk from a snapshot in seconds instead of hours.

245
00:10:57,560 --> 00:10:59,320
For disaster recovery that's massive.

246
00:10:59,320 --> 00:11:02,440
Spin up a full production copy of your environment in minutes.

247
00:11:02,440 --> 00:11:04,440
So that's the core of Azure disk storage.

248
00:11:04,440 --> 00:11:07,320
Build for durability, security and speed.

249
00:11:07,320 --> 00:11:08,600
Let's bring it all together.

250
00:11:08,600 --> 00:11:09,560
Four disk types.

251
00:11:09,560 --> 00:11:11,960
Standard SSD for budget-friendly dev and test.

252
00:11:11,960 --> 00:11:14,360
Premium SSD for reliable production performance.

253
00:11:14,360 --> 00:11:18,040
Premium SSD V2 for flexible high performance without the ultra-price.

254
00:11:18,040 --> 00:11:21,320
And ultra-disk for the extreme workloads where every microsecond matters.

255
00:11:21,320 --> 00:11:22,440
Here's the bottom line.

256
00:11:22,440 --> 00:11:24,440
Match the disk type to your workload.

257
00:11:24,440 --> 00:11:25,640
Not the other way around.

258
00:11:25,640 --> 00:11:27,720
Don't buy ultra-disk because it sounds impressive.

259
00:11:27,720 --> 00:11:30,920
Don't skimp on standard SSD if you're running a production database.

260
00:11:30,920 --> 00:11:32,440
Pick the right tool for the job.

261
00:11:32,440 --> 00:11:35,240
If this episode helped you make sense of Azure disk storage,

262
00:11:35,240 --> 00:11:38,440
subscribe and share it with someone starting their Azure journey.

263
00:11:38,440 --> 00:11:40,840
And tune in next time for another knowledge nugget.