Ticket #2157 (closed unplanned_task)
NFR_GENERAL_PERFORMANCE_R0
| Reported by: | kyli | Owned by: | kyli |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | uncategorized | Version: | 2.0 |
| Keywords: | Cc: | ||
| Category: | unknown | Effort: | |
| Importance: | Ticket_group: | ||
| Estimated Number of Hours: | 0 | Add Hours to Ticket: | 0 |
| Billable?: | yes | Total Hours: | 0 |
| Analysis_owners: | kyli | Design_owners: | kyli |
| Imp._owners: | kyli | Test_owners: | |
| Analysis_reviewers: | pap | Changelog: | Changelog |
| Design_reviewers: | meddle | Imp._reviewers: | meddle, deyan |
| Test_reviewers: | Analysis_score: | 3.5 | |
| Design_score: | 3.5 | Imp._score: | 3.5 |
| Test_score: | 0 |
Description
Change History
comment:2 Changed 15 years ago by kyli
- Owner set to kyli
- Status changed from new to s1a_analysis_started
comment:3 Changed 15 years ago by kyli
- Status changed from s1a_analysis_started to s1b_analysis_finished
comment:4 Changed 15 years ago by pap
- Status changed from s1b_analysis_finished to s1c_analysis_ok
- Analysis_reviewers set to pap
- Analysis_score changed from 0 to 3.5
- OK but it would be nice if you gave some measurements of the expected improvement.
comment:5 Changed 15 years ago by kyli
- Design_owners set to kyli
- Status changed from s1c_analysis_ok to s2a_design_started
comment:6 Changed 15 years ago by kyli
- Status changed from s2a_design_started to s2b_design_finished
There are some measurements on the last bullet of each paragraph, e.g. : The visibility thing result in smooth text writing, the halo menus improve "open preview" speed with about 5 secs (on my PC) and 170 less bound controls for every opened book.
comment:7 Changed 15 years ago by kyli
A, yeah, startup time changed from 22 to 16 :) Not sure whether this is from me..
comment:8 Changed 15 years ago by meddle
- Status changed from s2b_design_finished to s2c_design_ok
- Design_score changed from 0 to 3.5
- Design_reviewers set to meddle
I think the design is good for performance design, but you 'refactor' some things as with the halos, so without tests that everything stays OK, I think is a little bit dangerous. Write tests after the release the review procedure will change and the test checks will be more important, also the test quality will be taken into account!
And may be is from you and the visibility changes... but we will see...
3.5p
comment:9 Changed 15 years ago by kyli
- Status changed from s2c_design_ok to s3a_implementation_started
comment:10 Changed 15 years ago by kyli
- Status changed from s3a_implementation_started to s3b_implementation_finished
- Imp._owners set to kyli
comment:11 Changed 15 years ago by meddle
- Cc kyli added
- Status changed from s3b_implementation_finished to s3c_implementation_ok
- Imp._score changed from 0 to 3.5
- Imp._reviewers set to meddle, deyan
So... good performance...
- The haloSync prop in AppMainWindow, depended on a property 'lastCurrentArea' or something and and it set it... that is bad, I removed the property and replaced it with a field.
- Don't use names like 'd', 'c', 'hm'... especially 'hm'... bad practice, I will live them and in your next task replace them with proper ones...
3.5p
comment:12 Changed 15 years ago by deyan
- Status changed from s3c_implementation_ok to closed
Batch update from file query-10.csv
