IEEE Transactions on Software Engineering · 1995 · 94 citations · 12 references
ComputingComputer ScienceComputer SystemsComputer NetworksDistributed SystemsQueuing TheoryClient-server ArchitecturePerformance Bottleneck AnalysisPerformance ModelingQueueing ProcessesQueueing SystemsQueueing TheoryClient-server CommunicationContention ManagementContention ModelingNetwork ContentionPerformance ConstraintsRendezvous CommunicationResource Contention AnalysisSystem Performance Modeling
Software bottlenecks are performance constraints caused by slow execution of a software task, in typical client-server systems a client task must wait in a blocked state for the server task to respond to its requests, so a saturated server will slow down all its clients. A rendezvous network generalizes this relationship to multiple layers of servers with send-and-wait interactions (rendezvous), a two-phase model of task behavior, and to a unified model for hardware and software contention. Software bottlenecks have different symptoms, different behavior when the system is altered, and a different cure from the conventional bottlenecks seen in queueing network models of computer systems, caused by hardware limits. The differences are due to the "push-back" effect of the rendezvous, which spreads the saturation of a server to its clients. The paper describes software bottlenecks by examples, gives a definition, shows how they can be located and alleviated, and gives a method for estimating the performance benefit to be obtained. Ultimately, if all the software bottlenecks can be removed, the performance limit will be due to a conventional hardware bottleneck.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">></ETX>
12
Quantitative System Performance.
Edward D. Lazowska, John Zahorjan, G. Scott Graham et al. · Int. CMG Conference · 1985 · 384 citations
Joel F. Bartlett · ACM SIGOPS Operating Systems Review · 1981 · 249 citations