~/talk

Early Performance Testing: Finding News You Can Use

links:none on file
slides:none on file

Argues for fast, cheap, repeatable checks instead of one costly end-of-project simulation: run small synthetic workloads (notably a 10x10 test or 1x100 runs, even a 17-second slam) daily to detect regressions, use Fiddler or profilers to find root causes, keep a single-server calibration to track deltas, and run soak tests to catch leaks. Recommends JMeter or simple home-grown tools, CI integration (Jenkins/TeamCity), playback of production logs, and targeted tests for login, session creation, message bus capacity and database hotspots.

AI-written summary · about

  1. 0:00Start
  2. 0:48Iterative Development
  3. 1:55The Risks That We Address with Performance Testing
  4. 2:28Scalability
  5. 3:41Test for Capacity
  6. 10:40Indictment of the Traditional Simulation Test
  7. 12:06Make Automation Easier To Live with
  8. 13:32Horizontal Scalability
  9. 13:55Calibration
  10. 18:33Soap Tests
  11. 31:27Logging Response Times for Common Activities
  12. 31:49Reporting on Performance Results
  13. 37:02The Simulation Test
  14. 38:07Business Logic Layer
  15. 38:27Authentication Store
  16. 47:00Jmeter for Starting with Performance Testing
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.