Transactions per second

(also TPS, events per second)

Transactions per second definition

Transactions per second (TPS) measures the performance and capacity of a system that processes transactions. The metric specifies how many transactions the system can process in a second. Thereby, it is a key indicator of speed and efficiency. Organizations can also use transactions per second (TPS) to measure their system’s ability to process and respond to security-related events in real-time, such as threat detection and mitigation, access requests, or security event logging and analysis.

See also: active attack, information processing

High TPS vs. low TPS

High TPS implies that the system can process a larger volume of transactions per second, making it desirable for efficient business operations. It is essential for high-demand scenarios like blockchain networks or high-volume payment systems. A high TPS also enables the system to respond quickly to security threats and prevent or mitigate potential attacks because it efficiently processes many security events, such as log entries, network packets, or user requests, in real-time.
Low TPS means the system can process fewer transactions per second, leading to slower processing times and potential performance issues. Sometimes, a low TPS can prevent the company from handling its daily transactions, causing delays, failures, or even security vulnerabilities. So, a low TPS might only be acceptable for systems that process a small number of transactions daily.

High transactions per second (TPS) advantages

Enables real-time processing and response to security-related events.
Enables organizations to scale up or down to handle different traffic levels.
Allows for more effective resource utilization.
Helps the cybersecurity system reduce the potential impact of a security breach.
Helps organizations to better comply with regulatory requirements.