PRO_LIB_CORE_PERFORMANCE_R0

[Astea]

wiki page: PRO_LIB_CORE_PERFORMANCE_R0 - effort: 1d

[deyan]

Adding category

[deyan]

Correcting category

[niki]

taken

[boyan]

You need to change the following things:

• Add the task name to the ticket query (where it says TASK_NAME_HERE) so that the ticket is displayed.
• The research for bottlenecks is part of the design and implementation phases and should not be in a separate document.
• There might not be enough time for making new tests at this revision - list this as an optional task requirement.
• 1d is not enough for going to the code and reviewing algorithms - better use some kind of profiler to measure the performance (see PLATFORM_NFR_EFFIECENCY_R0 for some ideas).
• I think that PRO_LIB_CORE_MEMORY_MANAGEMENT_R0 and PLATFORM_NFR_EFFIECENCY_R0 should be added to the Related section.
• The How to demo section might include showing the results from the profiler before and after the improvements.
• Improve your English :)

[niki]

made some changes

[gogov]

• In each section where you list multiple things which should be done or noted or whatever, separate them in a more readable form with the appropriate bullets and indentation. Fix them.
• The task's name is about "performance", so no need to use "efficiency", because this could cause ambiguities and raise questions from the person who reads the analysis
• Make a note on what kind of performance is measured/optimized - runtime or memory (or something else?)
• Improve your English even more for obvious mistakes, so it's easier to read (:

[boyan]

The analysis is clear and detailed, with correct task requirements.

[deyan]

Batch update from file query-obsoleted.csv