What data for this category looks like
Teams collect data for this category from engine Profiler, crash platforms, real-device testing, and frame rate collection tools. Teams produce daily documents including performance test reports, device adaptation lists, optimization records, and crash analysis reports. Update frequency follows a daily or per-version iteration cycle. Fields include frame rate values, package size, resource loading duration, crash log ID, and more. Common units are frames per second (fps), megabytes (MB), and milliseconds (ms). Core data focuses on frame rate stability, resource usage, and loading efficiency. Test results for multiple device adaptation scenarios must be covered.
What constraints do these characteristics impose on forms and interactions
This category’s data comes from scattered sources and updates frequently. External business systems or downstream nodes must implement functions to quickly load historical configurations by test cycle. External business systems must handle unit format configuration for fields. External business systems must also implement interaction logic for unit format verification of fields such as frame rate and package size. Multiple device adaptation requirements add additional constraints. External business systems must implement functions to group and configure optimization items by device dimension. The form for optimization effect regression must link to historical test data entries via external business systems or downstream nodes to avoid duplicate data entry. Errors in this workflow directly affect store reviews. External business systems must enforce mandatory field requirements and numerical validity verification for core performance indicators.
How to set configurations
This configuration applies to FastGPT v4.17.0.
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
Form input node formInput | Test example: Select 3 fields from game client performance optimization as mandatory inputs; actual fields are determined by the task | This node collects user input; when mandatory items are missing, interaction status must be checked to prevent downstream nodes from receiving incomplete input |
User selection node userSelect | Test example: Set 2 business options, check corresponding branches one by one | This node handles user selection; queries and filtering of game client performance optimization related records must be implemented by downstream interfaces or external systems |
| Field passing after submission | Test example: Prepare 10 game client performance optimization input samples covering complete filling, missing mandatory items, and cancel operations | Compare input and node output to verify whether downstream nodes receive corresponding fields; result thresholds are determined by actual tasks |
| External implementation item: Form field type | Must be implemented separately by external systems; use formInput for frame rate and package size, use userSelect for device list | Adapt input forms for different performance indicators; numeric fields support free input, preset fields reduce manual errors |
| External implementation item: Field unit format verification logic | Must be implemented separately by external systems; implemented by external business systems | Match unit requirements specific to this category such as fps, MB, ms; verification must be completed by external systems |
| External implementation item: Historical configuration loading function | Must be implemented separately by external systems; implemented by external business systems or downstream nodes | Adapt to daily or per-version update frequencies, reduce duplicate data entry |
Three common mistakes
- When selecting associated variables for performance test reports, front-end drag-and-drop lag and operational delays occur. The number of selectable items in
userSelectis not limited, and the large volume of historical test data loaded by external business systems causes excessive front-end rendering pressure. - Device group configuration entered in the form is not correctly associated with corresponding test data. The external business system does not complete the association binding between device groups and test data, resulting in mismatched group configuration and test results.
- An error reporting that core performance indicators are empty appears after submitting the form. The external business system does not set fields such as frame rate and package size as mandatory items, resulting in direct submission after missing key information.
How to confirm the configuration is complete
- Open the form configuration page, check whether the field types of
formInputanduserSelectmatch the corresponding business fields. - Simulate entering performance data for different devices, verify whether the unit format verification logic implemented by the external business system normally triggers format prompts.
- Retrieve historical configurations from the past 7 days, confirm whether the historical configuration loading function implemented by the external business system or downstream nodes can normally load test configurations for the same version.
- Submit a test form without filling in core performance indicators, verify whether the mandatory item verification implemented by the external business system normally blocks submission.
The values given are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.