22:
138:, not of the technology. Thick provisioning is typically more efficient when the amount of resource used very closely approximates to the amount of resource allocated. Thin provisioning offers more efficiency where the amount of resource used is much smaller than allocated, so that the benefit of providing only the resource needed exceeds the cost of the virtualization technology used.
131:
refer to an allocation scheme for any resource. For example, real memory in a computer is typically thin-provisioned to running tasks with some form of address translation technology doing the virtualization. Each task acts as if it has real memory allocated. The sum of the allocated virtual memory assigned to tasks typically exceeds the total of real memory.
205:
only dedicated when data is actually written by the application, not when the storage volume is initially allocated. The servers, and by extension the applications that reside on them, view a full size volume from the storage but the storage itself only allocates the blocks of data when they are written.
172:
With thin provisioning, storage capacity utilization efficiency can be automatically driven up towards 100% with very little administrative overhead. Organizations can purchase less storage capacity up front, defer storage capacity upgrades in line with actual business usage, and save the operating
168:
Thin provisioning, in a shared-storage environment, provides a method for optimizing utilization of available storage. It relies on on-demand allocation of blocks of data versus the traditional method of allocating all the blocks in advance. This methodology eliminates almost all whitespace which
231:
in banks. Much as all processes running on a computer whose memory is thinly provisioned may not simultaneously use the sum total of their allotments of memory because it does not all exist in the computer at one time; if all depositors to a bank simultaneously close their accounts by taking cash
204:
to view more storage capacity than has been physically reserved on the storage array itself. This allows flexibility in growth of storage volumes, without having to predict accurately how much a volume will grow. Instead, block growth becomes sequential. Physical storage capacity on the array is
130:
to give the appearance of having more physical resources than are actually available. If a system always has enough resource to simultaneously support all of the virtualized resources, then it is not thin provisioned. The term thin provisioning is applied to disk layer in this article, but could
169:
helps avoid the poor utilization rates, often as low as 10%, that occur in the traditional storage allocation method where large pools of storage capacity are allocated to individual servers but remain unused (not written to). This traditional model is often called "fat" or "thick" provisioning.
144:
allocation differs from thin provisioning. Most file systems back files just-in-time but are not thin provisioned. Overallocation also differs from thin provisioning; resources can be over-allocated / oversubscribed without using virtualization technology, for example
160:
systems. Thin provisioning allows space to be easily allocated to servers, on a just-enough and just-in-time basis. Thin provisioning is called "sparse volumes" in some contexts.
188:
products in early 2001. Previous systems generally required large amounts of storage to be physically pre-allocated because of the complexity and impact of growing volume (
208:
As a practical consideration, a storage manager needs to monitor actual storage used, adding additional storage capacity such as disks, tapes, solid-state drives (
324:
It was first offered by
StorageTek, prior to its acquisition by Sun Microsystems, in its Iceberg (mainframe) and Shared Virtual Array (SVA) (open systems) arrays
250:
286:
149:
seats on a flight without allocating actual seats at time of sale, avoiding having each consumer having a claim on a specific seat number.
39:
105:
359:
86:
58:
354:
245:
43:
65:
265:
72:
127:
54:
141:
32:
260:
157:
152:
Thin provisioning is a mechanism that applies to large-scale centralized computer disk-storage systems,
153:
228:
189:
255:
201:
181:
319:
79:
212:), etc. as necessary to satisfy the write requests of the server and residing application(s).
209:
173:
costs (electricity and floorspace) associated with keeping unused disk capacity spinning.
348:
291:
Since the days of VMware ESX 3, many IT folks have been wary of thin virtual disks...
146:
21:
236:
ensues, since their combined total usually exceeds the cash kept by the bank.
227:
There is an analogy between thin provisioning in computers and the keeping of
216:
185:
119:
176:
Thin technology on a storage virtualization frame was first introduced by
339:
233:
192:) space. Thin provisioning enables over-allocation or over-subscription.
135:
219:(STK) announced their Iceberg product in 1991 (released later in 1994).
134:
The efficiency of thin or thick/fat provisioning is a function of the
177:
287:"Thin provisioning myth-busters: The benefits of thin virtual disks"
200:
Over-allocation or over-subscription is a mechanism that allows a
15:
215:
The over-allocation concept was first introduced when
46:. Unsourced material may be challenged and removed.
8:
106:Learn how and when to remove this message
277:
7:
44:adding citations to reliable sources
14:
340:Wikibon thin provisioning article
20:
31:needs additional citations for
1:
303:"Iceberg finally thaws out".
376:
266:Fractional-reserve banking
320:"Thin Is In -- Or Is It?"
128:virtualization technology
251:Statistical multiplexing
360:Hardware virtualization
261:Storage virtualization
246:Logical Volume Manager
158:storage virtualization
355:Computer data storage
40:improve this article
318:Jon William Toigo.
229:cash reserve ratios
55:"Thin provisioning"
256:Storage hypervisor
182:VMware Workstation
180:as part of their
124:thin provisioning
116:
115:
108:
90:
367:
327:
326:
315:
309:
308:
300:
294:
293:
282:
111:
104:
100:
97:
91:
89:
48:
24:
16:
375:
374:
370:
369:
368:
366:
365:
364:
345:
344:
336:
331:
330:
317:
316:
312:
302:
301:
297:
285:Mike Laverick.
284:
283:
279:
274:
242:
232:withdrawals, a
225:
223:Banking analogy
198:
196:Over-allocation
166:
126:involves using
112:
101:
95:
92:
49:
47:
37:
25:
12:
11:
5:
373:
371:
363:
362:
357:
347:
346:
343:
342:
335:
334:External links
332:
329:
328:
310:
307:. May 2, 1994.
295:
276:
275:
273:
270:
269:
268:
263:
258:
253:
248:
241:
238:
224:
221:
197:
194:
165:
162:
114:
113:
28:
26:
19:
13:
10:
9:
6:
4:
3:
2:
372:
361:
358:
356:
353:
352:
350:
341:
338:
337:
333:
325:
321:
314:
311:
306:
305:Computerworld
299:
296:
292:
288:
281:
278:
271:
267:
264:
262:
259:
257:
254:
252:
249:
247:
244:
243:
239:
237:
235:
230:
222:
220:
218:
213:
211:
206:
203:
195:
193:
191:
187:
183:
179:
174:
170:
163:
161:
159:
155:
150:
148:
143:
139:
137:
132:
129:
125:
121:
110:
107:
99:
96:November 2006
88:
85:
81:
78:
74:
71:
67:
64:
60:
57: –
56:
52:
51:Find sources:
45:
41:
35:
34:
29:This article
27:
23:
18:
17:
323:
313:
304:
298:
290:
280:
226:
214:
207:
199:
175:
171:
167:
151:
142:Just-in-time
140:
133:
123:
117:
102:
93:
83:
76:
69:
62:
50:
38:Please help
33:verification
30:
147:overselling
349:Categories
272:References
217:StorageTek
186:VMware ESX
66:newspapers
120:computing
240:See also
234:bank run
164:Overview
136:use case
80:scholar
202:server
178:VMware
156:, and
82:
75:
68:
61:
53:
87:JSTOR
73:books
184:and
154:SANs
59:news
210:SSD
190:LUN
118:In
42:by
351::
322:.
289:.
122:,
109:)
103:(
98:)
94:(
84:·
77:·
70:·
63:·
36:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
