The Index · Performance optimisation
Performance optimisation
Profiling, flamegraphs, bundle size, load tests. THREE independent graders flagged its absence — it existed pre-O*NET-rederivation as `optimize-performance` and was lost in the rebuild, so profilers were landing in `debugging` or `observability`, neither of which is what a profiler is for. tashan measures 9 capabilities for this work and ranks them by tashan score — a transparent composite of upkeep, freshness and real adoption. How we measure ›
| # | Capability | tashan | Evidence | Health |
|---|---|---|---|---|
| 1 | Design | 76 | 3k ★ | active |
| 2 | Dev Tools & CI | 65 | 853/wk | active |
| 3 | Dev Tools & CI | 61 | 222/wk | active |
| 4 | Security | 55 | 123/wk | active |
| 5 | Dev Tools & CI | 40 | 1 marketplaces | active |
| 6 | Security | 37 | 7/wk | active |
| 7 | Design | 35 | 8 ★ | active |
| 8 | AI & Agents | 30 | 64/wk | abandoned |
| 9 | Dev Tools & CI | 23 | 1 ★ | active |
Who does this work
O*NET records this as a core process step for 31 occupations, including Automotive Engineering Technicians, Bioengineers and Biomedical Engineers, Civil Engineers, Computer Hardware Engineers, Computer Network Support Specialists, Computer Programmers, Computer Systems Analysts, Computer Systems Engineers/Architects, Computer User Support Specialists, Data Warehousing Specialists and others.
Recorded there as: "Test software performance" / "Recommend technical design or process changes to improve efficiency, quality, or performance". We publish it under the name practitioners use.
Other work
Occupational data from the O*NET 30.3 Database by the U.S. Department of Labor, Employment and Training Administration, used under CC BY 4.0. tashan consolidated its process steps into the terms practitioners use; O*NET does not endorse this site.