At first, we need to define the optimisation criteria and their
priorities.
Then we need to perform quick review of the source code and
design documents to find out which code should be analyzed.
For example, in the case of performance optimisation, it's
rather necessary to analyze fast-path code.
The quick review is also necessary for the feasibility study.
Thus, this stage is performed before the statement of work is approved.
For pure review we need the source code and documentation only.
For performance analysis and/or bug fixing we need the build
system and hardware as well.
However, the review activity may be started immediately after
obtaining of the source code.
The review of the code is performed and review reports are provided
to customer.
Measurement tests are implemented (source code is provided to customers).
This activity may start before hardware obtaining (tests can be
debugged using instrumental computer or simulator as system under test).
Then the tests are applied to the device and the results are stored.
They can be repeated after bottleneck fixing to evaluate their
effectiveness.
Then profiling is performed, bottlenecks are found and different
ways of their resolving are proposed.
OKTET Labs engineers will modify the source code according to solutions
approved by customer, debug the fixes and apply performance
measurement tests.
