|
|
| (7 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| | [[TPTP/Wiki_Usage_Ruls]] | | [[TPTP/Wiki_Usage_Ruls]] |
| | | | |
| − | [[TPTP/Profiler | Profiler]] | + | [[TPTP/Wiki_Tips]] |
| | | | |
| − | | + | [[TPTP_Profiler | Profiler]] |
| − | | + | |
| − | ===Notes==
| + | |
| − | ===Expectation===
| + | |
| − | == Our expectation from survey ==
| + | |
| − | If brief, we want to change profiler and support with feedback for product. :)
| + | |
| − | | + | |
| − | But if it takes more seriously.
| + | |
| − | TPTP Profiler is universal tool which provides broad range of functionality for applications tuning (execution, heap, threading). But as any other universal tools it suffers from difficulties with solving specific narrow problems. Right now in TPTP list of them isn't defined but it can be done in scope of Usability survey. Probably each Lead User's project has own set of such tasks and their identification is part of this initiative. When tasks will be defined and documented in Wiki we can turn to definition of most convenient approach for solving this task by TPTP profiler. Improving and making it valuable at least in some specific appliances can increase amount of users and attracts attention of certain community.
| + | |
| − | | + | |
| − | Crucial point is continuous collaboration between Lead User and TPTP representative. This interaction should be based on development schedule and also be iterative.
| + | |
| − | | + | |
| − | For us also important that Lead user's project bit by bit makes TPTP as a part of every day development process. Results if the survey will not relevant to is goals if TPTP remains which only used in own sandbox and only then new regular version released.
| + | |
| − | | + | |
| − | List:
| + | |
| − | - Project specific profiling task definition
| + | |
| − | -
| + | |
