The Sisyphus database retrieval software performance antipattern

Authors:
Robert F. Dugan, Jr.;Ephraim P. Glinert;Ali Shokoufandeh
Affiliations:
Stonehill College Easton, MA;Rensselaer Polytechnic Institute, Troy, NY;Drexel University, Philadelphia, PA
Venue:
WOSP '02 Proceedings of the 3rd international workshop on Software and performance
Year:
2002

Citing 6
Cited 4

AntiPatterns: refactoring software, architectures, and projects in crisis

AntiPatterns: refactoring software, architectures, and projects in crisis
Software performance antipatterns

Proceedings of the 2nd international workshop on Software and performance
Object-Oriented Design Heuristics

Object-Oriented Design Heuristics
Performance Engineering of Software Systems

Performance Engineering of Software Systems
Oracle8i: The Complete Reference (Book/CD-ROM Package)

Oracle8i: The Complete Reference (Book/CD-ROM Package)
Introduction to Algorithms

Introduction to Algorithms

Performance lies my professor told me: the case for teaching Software Performance Engineering to undergraduates

WOSP '04 Proceedings of the 4th international workshop on Software and performance
Performance problem diagnostics by systematic experimentation

Proceedings of the 18th international doctoral symposium on Components and architecture
Systematic guidance in solving performance and scalability problems

Proceedings of the 18th international doctoral symposium on Components and architecture
Supporting swift reaction: automatically uncovering performance problems by systematic experiments

Proceedings of the 2013 International Conference on Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

In this paper we propose the Sisyphus database retrieval software performance antipattern. The antipattern occurs in application designs that process large, frequently accessed lists stored in a relational database, but display only a small subset to the user. Software Performance Engineering (SPE) techniques are used to analyze the antipattern. Four solutions are evaluated: rownum and index, upper/lower bound, sequence numbering, and caching. We discuss the real world challenges of correcting this antipattern early in the application life cycle.