Engineering investigations
Performance and scale
Where time and money go as the data grows. Every claim here needs a measurement before and after.
- Slowest journeys, end to endPromptShows where the seconds go on the paths people actually use.
- Steps that wait for no reasonPromptFinds steps that wait for each other to finish when they could run at the same time.
- Queries that grow badlyPromptFinds the database queries that will be the first to slow down as tables grow.
- Work repeated for nothingPromptFinds work redone on every request or screen redraw when nothing it depends on changed.
- What breaks at ten times the sizePromptNames the first thing to break if the project takes off, before it does.
- Loops that blow up with big dataPromptFinds loops inside loops that are fine at 50 rows and painful at 50,000.
- Memory that keeps growingPromptFinds why a page or process gets slower or crashes the longer it runs.
- One slow step that blocks the restPromptFinds one slow step that makes every other request wait in line behind it.
- Parallel work with no limitPromptFinds work run in parallel with no limit, which can swamp the database connections or an outside service.