This smell occurs when a system spends more time “thrashing” than accomplishing real work because there are too many processes relative to available resources.
Solution: Quantify the thresholds where thrashing occurs (using models or measurements) and determine if the architecture can meet its performance goals while staying below the threshholds.
Smith, C. U., & Williams, L. G. (2003). More new software performance antipatterns: Even more ways to shoot yourself in the foot. Computer Measurement Group Conference.
All rights reserved (c) Tushar Sharma 2017-23.