DcoumentDB has a minimum billing time of 1 hour.
How much would the following cost?
I create a collection (400Ru/s) at time 01:00
I upgrade the collection 1000Ru/s to a total of 1400Ru/s at time 01:30
I downgrade the collection back to 400Ru/s at time 02:15
I delete the collection at 02:45
Will I be charged 400Ru/s for 2 hours + 1000Ru/s for 1 hour
Or
Will I be charged 400Ru/s + 1000Ru/s for 2 hours?
I ask as it would depend on how the billing clock works, I could see it being the latter as I was at 1400Ru/s at 01:00 & 02:00 hours. Although I only used the upgrade for less than 1 hour.
Great question! Based on the FAQs provided here, you will be charged for 1400RU/s for both hours. If I am understanding the FAQs correctly, you will be charged the maximum RU/s provisioned in a clock hour (i.e. between 1:00 and 2:00, 2:00 and 3:00 etc.)
From the documentation link:
What if my container is active for less than an hour?
You are billed the flat rate for each hour the container exists,
regardless of usage or if the container is active for less than an
hour. For example, if you create a container and delete it 5 minutes
later, your bill will reflect a charge for 1 unit hour.
When does the billing rate change after I upgrade a container?
If you define your own performance for a container and you upgrade at
9:30AM from 400 RUs to 1,000 RUs and downgrade at 10:45AM back to 400
RUs, you will be charged for two hours of 1,000 RUs.
Related
I'm trying to determine whether it is feasible from a cost perspective to use AWS Rekognition video streaming for short, scheduled streams on a camera network.
I understand that they bill $0.12/min for the service, however the docs are not clear if this is rounded to the nearest minutes per streaming invocation or at the end of the month.
This could result in a VERY drastic change in price when you have 1000s of cameras...
For example, if you stream 30 seconds per day for a month, are you billed for 30 minutes or 15 minutes?
15 mins.
From Rekognition price calculation page :
Usage charges are applied monthly and are pro-rated for partial minutes.
I have a LogicApp which runs for every 2 minutes. All runs in this LogicApp has failed between 4:45pm to 5:00pm.
when I check for the metric Run Failure Percentage under 'Metrics' in the Azure portal with time granularity as 15 minutes and aggregation as Average, it shows me Run Failure Percentage as 114.29% for time window 4:45 pm to 5:00 pm.
My question is, how the metric value is calculated? shouldn't it be less than 100 for percentage?
So I am super stuck with this question and don't even know where to start from. This is the info I have:
Start to Finish Number of People per Day roundtrip
Seattle to Bainbridge 5,847 passengers 14.4 miles
Seattle to Tacoma, WA 3,243 passengers 40.2 miles
Bainbridge to Tacoma, WA 746 passengers 42 miles
This whole system costs 20 million. I need to develop different prices for the roundtrip tickets in a way that will be fair and understaandable to everyone. If the costs go from 20- 22 million, the system should be felxible to adjust for that too. The hint is to use equation "y=mx+b". This is the only information that I am given. Can anyone please help me where to even start? My idea was that we should charge Tacoma,WA passengers the most money cause it's less people and longest miles, second we should charge Seatle-Tacoma,WA passengers and finally the least amount should be charged to Seattle-Bainbridge passengers because it's the least miles and most passengers. Can you guys help me formulate this in an excel and how to get a head start with this one. |
I would really aprreciate the help,
Thanks,
Nika
Consider charging all passengers a specific amount per mile. The more you charge per mile, the more revenue you will generate on a daily basis.
At a minimum, the mileage rate should be set to generate enough money to cover the daily operating costs and create a maintenance reserve.
If you increase the mileage rate beyond this, you will also generate a cash stream that you can use to retire 20 million investment. The greater the rate the quicker the payback!
On a Load Test with Loadrunner controller, I have a script which make 1029 Transactions per Hour with 1 Virtual User,with 1 "number of Iteration" ,"ignore think time", and pacing setting which start every iteration at a random interval every 3 to 4 seconds but I want to reduce the transactions to 45 Transactions per Hour. I set then the think time to "Limit think time to : 65", but without success.
Does anyone knows how to reduce the number of transactions. Is there any run time setting which must be changed to get this transactions reduced?
Use 'fixed' intervals of 80 seconds.
45 transactions per hour
3600 seconds in an hour
= 80 seconds per transaction
When we want a new Service Namespace for Access control and Service bus, it offers option for CONNECTION PACK SIZE as 0,5,25,100,500.
What does it indicate i.e number of active connections ...? If that is the case...? How does the connection pack size of 0 work out...???
It is complicated, but this is how I understand it:
Azure AppFabric SB connections are per "average connection month". The way it's calculated is that on a daily basis, they take the maximum number of connections at any given time, and then average the daily maximum over the month.
If you buy a pack, you get the connections at a rate of around $2/connection/month, if you don't buy a pack, the connections are charged pro rated at around $4/connection/month.
For example. If you have no packs, and you create 40 connections in one hour of one day (say month end reporting) - even though it's only an hour you are charged $4 x 40 for the day, but that's averaged over the month so you pay $4 x 40 / 30.
Now to consider packs - even though you hit a peak of 40 connections your average is around 1.3 connections/month = ~$6, so even purchasing a 5 connection pack at $10 is unnecessary.