# 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 end](https://atlasscope.dev/prompts/slowest-journeys-end-to-end): Shows where the seconds go on the paths people actually use.
- [Steps that wait for no reason](https://atlasscope.dev/prompts/steps-that-wait-for-no-reason): Finds steps that wait for each other to finish when they could run at the same time.
- [Queries that grow badly](https://atlasscope.dev/prompts/queries-that-grow-badly): Finds the database queries that will be the first to slow down as tables grow.
- [Work repeated for nothing](https://atlasscope.dev/prompts/work-repeated-for-nothing): Finds work redone on every request or screen redraw when nothing it depends on changed.
- [What breaks at ten times the size](https://atlasscope.dev/prompts/what-breaks-at-ten-times-the-size): Names the first thing to break if the project takes off, before it does.
- [Loops that blow up with big data](https://atlasscope.dev/prompts/loops-that-blow-up-with-big-data): Finds loops inside loops that are fine at 50 rows and painful at 50,000.
- [Memory that keeps growing](https://atlasscope.dev/prompts/memory-that-keeps-growing): Finds why a page or process gets slower or crashes the longer it runs.
- [One slow step that blocks the rest](https://atlasscope.dev/prompts/one-slow-step-that-blocks-the-rest): Finds one slow step that makes every other request wait in line behind it.
- [Parallel work with no limit](https://atlasscope.dev/prompts/parallel-work-with-no-limit): Finds work run in parallel with no limit, which can swamp the database connections or an outside service.

Source: https://atlasscope.dev/prompts/performance-and-scale