Difference between revisions of "Sample Project"
Chris Tyler (talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | = Project Name = | + | = Project Name = Profile and Improve RPM and YUM performance on the Pi |
<!-- Replace "Project Name" with the actual name of the project in the line above. --> | <!-- Replace "Project Name" with the actual name of the project in the line above. --> | ||
== Project Description == | == Project Description == | ||
| − | + | Profiling the YUM and RPM performance to identify which parts of the processes are taking time. After identifying, improve the performance. | |
== Project Leader == | == Project Leader == | ||
| − | + | Jose Giagonia | |
| − | |||
| − | |||
| − | |||
| − | |||
== Project Contributor(s) == | == Project Contributor(s) == | ||
| Line 25: | Line 21: | ||
== Project Plan == | == Project Plan == | ||
| + | |||
| + | Identify the tools fro profiling. | ||
| + | Initial testing phase of YUM and RPM without profiling. | ||
| + | Identify The processes which takes time. | ||
| + | Improve the processes. | ||
| + | Test again and take note of the results. | ||
=== Tracking === | === Tracking === | ||
| Line 36: | Line 38: | ||
Goals for each release and plans for reaching those goals: | Goals for each release and plans for reaching those goals: | ||
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | <!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | ||
| − | * 0.1 | + | * 0.1 Identify which part of YUM and RPM spends alot of time. |
| − | * 0.2 | + | * 0.2 An improvement in performance. |
| − | * 0.3 | + | * 0.3 A package that is improved for Pi. |
== Communication == | == Communication == | ||
Revision as of 20:04, 20 October 2013
= Project Name = Profile and Improve RPM and YUM performance on the Pi
Contents
Project Description
Profiling the YUM and RPM performance to identify which parts of the processes are taking time. After identifying, improve the performance.
Project Leader
Jose Giagonia
Project Contributor(s)
Project Details
Project Plan
Identify the tools fro profiling. Initial testing phase of YUM and RPM without profiling. Identify The processes which takes time. Improve the processes. Test again and take note of the results.
Tracking
Key contacts
Goals by Release
Goals for each release and plans for reaching those goals:
- 0.1 Identify which part of YUM and RPM spends alot of time.
- 0.2 An improvement in performance.
- 0.3 A package that is improved for Pi.
