{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:58:20Z","timestamp":1750309100599,"version":"3.41.0"},"reference-count":2,"publisher":"Association for Computing Machinery (ACM)","issue":"2","license":[{"start":{"date-parts":[[2023,4,30]],"date-time":"2023-04-30T00:00:00Z","timestamp":1682812800000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["Queue"],"published-print":{"date-parts":[[2023,4,30]]},"abstract":"<jats:p>You don't need to do a full-scale benchmark any time you have a performance or capacity planning problem. A simple measurement will provide the bottleneck point of your system: This example program will get significantly slower after eight requests per second per CPU. That's often enough to tell you the most important thing: if you're going to fail.<\/jats:p>","DOI":"10.1145\/3595862","type":"journal-article","created":{"date-parts":[[2023,5,24]],"date-time":"2023-05-24T22:28:11Z","timestamp":1684967291000},"page":"54-65","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["You Don't know Jack about Application Performance"],"prefix":"10.1145","volume":"21","author":[{"given":"David","family":"Collier-Brown","sequence":"first","affiliation":[],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2023,5,24]]},"reference":[{"volume-title":"Analyzing Computer System Performance with Perl::PDQ","author":"Gunther N. J.","key":"e_1_2_1_1_1","unstructured":"Gunther, N. J. 2005. Analyzing Computer System Performance with Perl::PDQ. New York: Springer; http:\/\/www.perfdynamics.com. (I particularly recommend Gunther's Guerrilla Capacity Planning)."},{"key":"e_1_2_1_2_1","unstructured":"Teamquest Predictor formerly Teamquest Model; https:\/\/www.fortra.com\/blog\/teamquest-acquisition-two-and-half-years-later."}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3595862","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/3595862","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T22:48:39Z","timestamp":1750286919000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3595862"}},"subtitle":["Knowing whether you're doomed to fail is important when starting a project."],"short-title":[],"issued":{"date-parts":[[2023,4,30]]},"references-count":2,"journal-issue":{"issue":"2","published-print":{"date-parts":[[2023,4,30]]}},"alternative-id":["10.1145\/3595862"],"URL":"https:\/\/doi.org\/10.1145\/3595862","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2023,4,30]]},"assertion":[{"value":"2023-05-24","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}