News in brief : From August 1, we are changing prices. Significant changes: the price of outgoing traffic decreases from 1 ruble per GB to 64 kopecks per GB, disk operations increase from 3 rubles per million to 5 rubles per million. The remaining prices vary slightly, the explanation of "why" below. In addition, we translate official prices from the value of "price per hour" to "price per second." Official prices are listed at the end of the article, in the table below they are given with fractional kopecks and calculated “per hour” for comparison with old prices.

Resource	Old prices	New prices
CPU time	1 ruble per hour	↓ 90 kopecks per hour
RAM	50 kopecks per GB * h	↑ 57.6 kopecks per hour
Disk operations	3 rubles per million	↑ 5 rubles per million
Read / write data	10 kopecks per GB	10 kopecks per GB
Data storage	5 rubles per TB * h	↓ 4.5 rubles per TB * h
Incoming traffic	20 kopecks per GB	↓ 16 kopecks per GB
Outbound traffic	1 ruble per GB	↓ 64 penny per GB

We change prices with two goals: first: a change in pricing (disk operations and Internet traffic), the second is price adjustment for more accurate accounting and write-off. In general, they were planned to be carried out separately, but the commercial department quite rightly noted that it is better to combine these changes, and not to distract customers once more.

IOPS are more expensive, traffic is cheaper

Let's not hide, the load on the disks is the most unpleasant problem for the cloud. Based on the concept of the cloud “for your money - even dance on your head”, we adjusted the prices so as to receive sufficient compensation for the uncomfortable load for us.
')
Reducing the price of traffic is a step towards large customers, for whom the outgoing traffic costs sometimes reach 50% of the total costs.

In addition, the administrators of our clients do not have special reserves to reduce traffic (well, do not you save on closing tags from td / tr / li?). But there are plenty of opportunities for optimizing disk load - and the increase in prices will probably make some of our clients think a little about caching, optimal read requests and database configurations.

According to our observations, for virtual machines with approximately the same consumption of traffic, memory and processor, the difference in the load on disk operations can reach a couple of orders of magnitude.

Transition from hours to seconds

Much more important from a technical point of view is the event: the transition from prices for “something per hour” (machine time, memory, data storage) to similar values ​​in seconds. The reason is very complicated.

We write off money (theoretically) with second accuracy. But - only whole pennies. In other words, as long as we don’t count a client with a whole amount of kopecks and a whole amount of resources, we don’t charge money from the account. This leads to a very bad problem. If we have an hour of computer time (3600 seconds) worth 100 kopecks, how much does one second of the processor cost? 100/3600 ... an ugly fraction, right? The same applies to prices for all other quantities associated with the hour. Ugly, uncomfortable.

It was decided that prices should be well expressed in seconds, and the amount of resources per penny should be the final fraction.

The result was a slight change in the rest of the prices.

Official

From 1.08.2011 new rates are introduced for renting computing resources in the Selektel cloud. Tariffing for units, previously measured in units, multiples of hours, is converted into units, units of seconds.

New prices (human readable version is given approximately and is not a legal value).

Resource	Official prices	Human readable option
CPU time	25 kopecks per kilosecond	90 kopecks per hour
RAM	16 kopecks per TB * s	57.6 kopecks per GB * hour (1.38 kopecks per MB * day)
Disk operations	5 rubles per million	5 rubles per million
Read / write data	10 kopecks per GB	10 kopecks per GB
Data storage	1 ruble 25 kopecks per PB * s	4.5 rubles per TB * h (10.8 kopecks per day Gb)
Incoming traffic	16 kopecks per GB	16 kopecks per GB
Outbound traffic	64 kopecks per GB	64 kopecks per GB

When we chose prices, we tried to make the change the minimum - in terms of aggregate consumption (revenue) in the cloud it would be about one percent.

Afterword

I hope that the reduction in the cost of outgoing traffic will appeal to our large customers, and the increase in the cost of disk operations will make those users whose applications are ... not very optimal.