SIS preliminary assessment tools
Practical system assessment tools for organizations
Select only the essential inputs. The tools provide both an executive-friendly summary and technical detail for discussion with IT or development teams.
Manual Task Cost Assessment
Estimate repetitive work hours and monthly people cost.
Excel to system readiness checker
Assess risk from business data scattered across spreadsheets.
Project Size Estimator
Estimate rough scope, project size, and early budget range.
Performance Testing Assessment
Estimate RPS, TPS, and system performance risk.
Production Readiness Assessment
Review eight operational layers required before go-live.
Tool 04
Performance Testing Assessment
Estimated load overview
Operating metrics for capacity planning
This example translates the selected inputs into a view similar to Google Analytics Realtime. Users in the latest 30 minutes are not the same as direct concurrent users.
Users in the last 30 minutes
20,625
Estimated range: 20,625
Realtime overview
GA RealtimeBase RPS
229.2
req/sec
Peak RPS
687.6
req/sec
Base TPS
41.26
tx/sec
Peak TPS
123.77
tx/sec
DB QPS
756.36
q/sec
Infrastructure Recommendation
High-throughput application structure
Suitable for systems with periodic traffic spikes and capacity headroom for peak periods.
Area to inspect first
database
What to check next
response time, error rate, slow query, CPU/memory, and external API latency should be checked together with a real load test.
This section is a simulated view for explanation only. It is not real Google Analytics data from the website.
Plain-language summary
A technical architecture review is recommended
Peak traffic may create bottlenecks, especially for transactions that write data concurrently.
Technical details+
Google Analytics interpretation
If GA Realtime shows 20,625 users in the latest 30 minutes, this is roughly 2,063-5,500 concurrent users. The selected active-time assumption uses 3,438 concurrent users for the RPS/TPS estimate.
- GA Realtime reference
- 20,625
- users / 30 min
- Estimated concurrent users
- 2,063-5,500
- 5 min active
- Used for calculation
- 3,438
- Recommended app instances
- 6 instances
Calculation assumptions: Requests per user per minute = 4, peak multiplier = 3x, transaction ratio = 18%, cache hit rate = 45%
This result is an initial estimate based on the selected assumptions. It is not a quotation, a confirmed load test result, or an architecture guarantee.
Performance Testing Guide
Key metrics to understand before performance testing
Use this section as a practical reference before planning a load test, checking a live system, or setting performance goals with a technical team.
Concurrent Users
Users active at the same time
The number of users using the system during the same period. This helps estimate overall pressure on the system.
RPS
Requests Per Second
The total number of requests per second, such as page views, API calls, data loading, and form submissions.
TPS
Transactions Per Second
The number of important business transactions per second, such as saving data, confirming orders, booking, or submitting forms.
Peak Multiplier
Peak-load multiplier
A multiplier used to reserve capacity for periods above normal usage, such as campaigns, launches, or deadline-driven traffic.
DB QPS
Database queries per second
The expected number of database queries per second after cache effect is applied. This helps identify database risk.
Cache Hit Rate
Requests served from cache
The share of requests answered from cache without reading the database again. Better cache reduces load and response time.
Response Time
System response time
How long the system takes to respond. It should be measured with averages and percentiles such as p95 or p99.
Error Rate
Failed request ratio
The share of failed requests during actual use or load testing. It is useful for evaluating reliability and readiness.
Learn more from official references