Background:
- Complex business
- Wide range of interfaces
- High degree of concurrency
- Large number of visits
Focus Point:
- Performance Index
- The association between modules
- Combination of knowledge and methodology
3 Types of performance problems:
- Performance failure is occurring
- The trouble has happened, and it's automatically good.
- The fault hasn't happened yet, but on the way to happening
Overall optimization ideas:
- The important premise:
- Understand the characteristics of the business
- Master Baseline Information
- Ensure ordered tuning:
- First platform after application
- First whole after local
- Dynamic re-static first
- See Time consumption distributions:
- Overall distribution of response time
- The analysis time is consumed in which modules, applications, and SQL.
- Application Optimization Five steps:
- System Research
- Business background
- Industry in which
- Use the crowd
- Load conditions
- Number of online users
- Peak hours
- Technical framework:
- Software and Hardware Checklist:
- Application Software Deployment Checklist:
- Front desk
- Background
- Data
- Hardware Platform Checklist:
- Host
- Internet
- Storage
- Schema topology diagram
- Interface Condition Description
- System type
- Type of Business
- Production-Type 7x24
- Auxiliary type can stop
- Type of transaction
- Oltp
- Olap
- OLTP and OLAP mixed
- Master Baseline Information
- Database
- Host
- Understand the state of the system
- The fault is in progress
- The fault has occurred, and the automatic reply
- The fault will come
- Information collection
- Deploy third-party monitoring tools:
- Ffcs_itsm
- Dt
- I3
- NMON
- System comes with tools:
- Platform Information
- Dynamic
- Static
- AWR, ADDM, ASH
- Jvm
- Various logs
- Write your own script tool:
- Problem Locator:
- Positioning means:
- System Resource situation
- Response Time Mode:
- Time distribution of the entire life cycle of a single transaction
- The time distribution of the overall transaction of the whole system
- Location Purpose:
- Internal system problem or external interface problem
- The whole problem or the local problem
- Overall issues
- Overall database issues
- Front and back applications
- Local issues
- A module is slow
- A menu is slow
- Resource issues or application issues:
- Resource issues
- Insufficient platform hardware
- Other programs run out of resources
- Application issues
- Which application area to drop in
- Which interface module to drop
- Which specific method or SQL to fall into
- Analytical Solutions
- Resource Utilization Analysis:
- Analysis:
- Insufficient CPU Memory IO
- Network card traffic is too large
- Storage failure
- Solve:
- Scaling strategy:
- Replace Server, Store
- Increase CPU memory, etc.
- Resource reorganization:
- Remove unrelated apps
- Adjust resource allocation
- According to the full-day pressure situation, staggered running resources
- Depending on how busy the machine is, it is reasonable to allocate different applications on different hosts.
- Application Analysis:
- Application Analytics Solutions
- Java
- GC Hangs too large
- WebLogic parameter configuration is incorrect
- C + +
- Database Analysis Solution:
- Code issues:
- Sql
- Plsql
- Model Design Issues
- Design of the table
- Design of the Index
- Paradigm
- Parameter issues
- Schema Analysis Solution:
- Cache
- Asynchronous
- Parallel
- Distribution
- Focus
- Summary tracking:
- Summarize:
- This tuning report
- This implementation of various documents
- Lessons learned:
- Lack of pre-launch performance stress testing:
- LoadRunner
- Ffcs Test Tool
- Improper operation:
- Not patched according to specifications
- Feature upgrade introduces Bugs
- Insufficient forecast of future business development
- Lack of skills in development and maintenance personnel
- Tracking:
- Daily Patrol
- Trend Analysis
- Related training
- Summary of this tuning case
- Similar case sharing
The methodology of system optimization