performance testing improving,too much to say

My friend and I discuss something on how our performance improvement in the future, we just talk about something below during 30 minutes,but not all stuff:

Version control,maintenance
- script
- result/raw data
- log

Env (server esp xeon, build control) common service perf test env and schedule

metrics (complete set used in tuning, typical set used in daily tracking)
- LR/JMeter: DB size, concurrent user, think time, env, 90% line... load resource
- other: log, os...

LR or JMeter
- understand difference and which one to choose

Process/scheduling - daily/formal

knowledge (tuning, isolation...)
- accumulate / display in organized way
- sharing

planning (case design)

script wring
- error handling
- common practice/F&Q

simulate real load
- prod monitor
- reflect to local env
- PPM/BAC

profiling tool

app profile log and log analyzer

test on load balanced env

stress test (analyze the throughput, trend and Knee)

single step test (resource, SQL happened, YSLOW...)

analyze & tuning
- Deployment diagram
- SQL (deadlock, lock)
- app code
- DB
- JBoss/JVM
- Apache (esp ability of analyze log then find bottleneck
- Load balance/cluster
- Hardware load balancer
- Front end
- CPU
- memory
- App thread
- Disk IO
- Network