Literature review
Bottleneck research found
Last updated
Bottleneck research found
Last updated
A performance evaluation of these benchmarks on commodity hardware identified bottleneck resources for each case.
The online bookstore's bottleneck was the database CPU
front-end and the back-end a bottleneck. With amounts of memory common by today’s standards, neither the main memory nor the disk proved to be a limiting factor in terms of performance for any of the benchmarks.
For document transfer applications like FTP, Gopher, and the World Wide Web, transfer time is directly related to available bandwidth. This depends on the path capacity between client and server and the competing traffic on that path. If applications had access to these measurements, they could calculate path utilization and select the best path or server to reduce response time. This dynamic server selection would be particularly useful in mobile computing environments with frequently changing server availability.
performance measurements with OPC UA client/server and pub/sub communication and created a CPU utilization prediction model based on linear regression that can be used to size hardware environments. We found that the server CPU is the main bottleneck for OPC UA pub/sub communication, but allows a throughput of up to 40,000 signals per second on a Raspberry Pi Zero. We also found that the client/server session management overhead can severely impact performance, if more than 20 clients access a single server.