Scientific Calculator

Everyday cloud and engineering maths with a scientific calculator

Most cloud work involves quick calculations: sizing, costs, growth and unit conversions. A scientific calculator with powers, logarithms and memory handles all of them without opening a spreadsheet. Here are worked examples you can type straight in.

Powers of two: storage, memory and subnets

• Addresses in a subnet: a /24 has 2^(32-24) = 256 addresses. In an AWS VPC, 5 of those are reserved in each subnet, leaving 251 usable. For full subnet details, use the IPv4 Subnet Calculator.
• Binary units: 1 GiB = 2^30 = 1,073,741,824 bytes, while 1 GB = 10^9 bytes. That's a 7.4% difference, which explains why a "500 GB" volume shows less space in the operating system.
• Data-size checks: how many 4 KB items fit in a 400 KB DynamoDB item limit? 400 / 4 = 100.

Logarithms: "how many steps" questions

• Bits needed for N values: log2(N), worked out as log(N) / log(2). For 1,000 IDs that's about 9.97, so you need 10 bits.
• Doubling time: if traffic grows 8% a month, it doubles after log(2) / log(1.08) ≈ 9 months. That's useful for planning when you will hit a service quota. Compare it with the defaults in the Service Quota Planner.
• Retries with exponential backoff: with a 100 ms base delay that doubles each time, the 6th retry waits 100 × 2^5 = 3,200 ms. Add up the series to make sure the total stays within a Lambda or contact flow timeout.

Cost and growth

• Compound growth: 10,000 calls a month growing 5% monthly reach 10000 × 1.05^12 ≈ 17,959 calls a month after a year.
• Per-minute pricing: 2,500 calls × 4.5 minutes × $0.018 per minute = $202.50. For a full Amazon Connect estimate covering voice, chat, telephony and add-ons, use the Connect Pricing Calculator. For generative AI costs, use the Bedrock Pricing Calculator.
• Percentages: a reserved price of $0.62 against an on-demand price of $1.00 is a saving of (1 − 0.62/1.00) × 100 = 38%.

Contact centre staffing basics

• Traffic intensity in Erlangs: calls per hour × average handle time in hours. 300 calls an hour with a 6-minute AHT gives 300 × 6/60 = 30 Erlangs, meaning about 30 agents busy at any moment before allowing for service level and shrinkage.
• Shrinkage: if 30 agents are needed on the phones and shrinkage is 30%, schedule 30 / (1 − 0.30) ≈ 43 agents.
• Occupancy: workload ÷ agents. 30 Erlangs across 34 agents is about 88%, which is high to sustain over a whole shift.

Tips for using the calculator

1. Use brackets generously. 100 × 2^5 and (100 × 2)^5 are very different numbers.
2. Check whether trigonometric functions are in degrees or radians before using them.
3. Store intermediate results in memory instead of retyping long decimals, which avoids rounding drift.
4. For time conversions, such as epoch seconds to dates, the Unix Timestamp Converter is faster and handles time zones.

The calculator runs entirely in your browser, works offline once loaded, and keeps nothing you type.