mirror of
				https://github.com/nickpoida/og-aws.git
				synced 2025-03-09 15:40:06 +00:00 
			
		
		
		
	Added cost gotcha around provisioned IOPS
This commit is contained in:
		
							parent
							
								
									35de351bd1
								
							
						
					
					
						commit
						a5afd9c7e0
					
				
					 1 changed files with 1 additions and 0 deletions
				
			
		|  | @ -969,6 +969,7 @@ EBS | |||
| -	⏱A worthy read is AWS’ [post on EBS IO characteristics](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-io-characteristics.html) as well as their [performance tips](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html#d0e86148). | ||||
| -	⏱One can [provision IOPS](http://aws.amazon.com/ebs/details/) (that is, pay for a specific level of I/O operations per second) to ensure a particular level of performance for a disk. | ||||
| -	⏱A single EBS volume allows 10k IOPS max. To get the maximum performance out of an EBS volume, it has to be of a maximum size and attached to an EBS-optimized EC2 instance. | ||||
| - 	💸Standard EBS volumes improve IOPS with size. It may make sense for you to simply enlarge a volume instead of paying for better performance explicitly. This can in many cases reduce costs by 2/3.  | ||||
| -	A standard block size for an EBS volume is 16kb. | ||||
| 
 | ||||
| ### EBS Gotchas and Limitations | ||||
|  |  | |||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue