# Next Steps

## In this learning path

- [Introduction](https://learn.arm.com/learning-paths/servers-and-cloud-computing/memory-subsystem/)
- [Identify Arm CPU topology, cache hierarchy, and NUMA configuration](https://learn.arm.com/learning-paths/servers-and-cloud-computing/memory-subsystem/system-overview/)
- [Analyze Arm cache hierarchy and performance characteristics](https://learn.arm.com/learning-paths/servers-and-cloud-computing/memory-subsystem/cache-hierarchy/)
- [Measure Arm cache and memory latency using ASCT pointer chase](https://learn.arm.com/learning-paths/servers-and-cloud-computing/memory-subsystem/pointer-chase-latency/)
- [Measure Arm single-core memory bandwidth with ASCT](https://learn.arm.com/learning-paths/servers-and-cloud-computing/memory-subsystem/streaming-bandwidth/)
- [Measure Arm multi-core memory bandwidth and loaded latency with ASCT](https://learn.arm.com/learning-paths/servers-and-cloud-computing/memory-subsystem/multicore-bandwidth/)
- [Compare Arm memory subsystem performance across systems](https://learn.arm.com/learning-paths/servers-and-cloud-computing/memory-subsystem/comparative-analysis/)
- [Next Steps](https://learn.arm.com/learning-paths/servers-and-cloud-computing/memory-subsystem/_next-steps/)

## Explore related resources
Find more information about the topics in this Learning Path:

- [Inside Nvidia GB10's Memory Subsystem, from the CPU Side](https://chipsandcheese.com/p/inside-nvidia-gb10s-memory-subsystem)
- [Memory latency for application software developers](https://learn.arm.com/learning-paths/cross-platform/memory-latency/)
- [Arm Neoverse N1 Software Optimization Guide](https://developer.arm.com/documentation/109896/latest/)
- [Arm Neoverse V2 Software Optimization Guide](https://developer.arm.com/documentation/109898/latest/)

## Review frequently asked questions

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

### Which ASCT benchmarks should I run to cover latency and bandwidth?
Use `pointer-chase` for cache and memory latency. Run the single-core bandwidth sweep for per-core throughput, then use `peak-bandwidth` and `loaded-latency` to assess multi-core scaling and latency under bandwidth pressure.

### What should I verify about the system topology before running benchmarks?
Confirm the core count, cluster layout, private and shared cache levels, and NUMA configuration. Use the baseline to interpret performance cliffs and bandwidth scaling.

### What result should I expect from the pointer-chase latency test?
Look for stepwise latency increases as the working set exceeds L1, L2, any shared cache, and finally DRAM. Use the plateaus and jumps to estimate the effective latency of each level.

### How should I compare results across Arm systems, such as different Graviton generations?
Run the same ASCT benchmarks with consistent settings and similar conditions on each system. Compare latency plateaus, bandwidth peaks, and multi-core scaling while accounting for differences in core topology and cache hierarchy.

### How should I interpret the NOP count in loaded-latency results?
Treat higher NOP counts as lower bandwidth pressure and zero NOPs as saturation. Look for the knee where latency starts climbing steeply as bandwidth increases.
