Closed
Bug 112213
Opened 23 years ago
Closed 15 years ago
Use timeline for perf measurements of folder and message loading
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: vparthas, Unassigned)
Details
Attachments
(3 files, 1 obsolete file)
7.83 KB,
text/html
|
Details | |
3.48 KB,
patch
|
mscott
:
superreview+
|
Details | Diff | Splinter Review |
588 bytes,
patch
|
mscott
:
superreview+
|
Details | Diff | Splinter Review |
Use timeline for perf measurements of folder and message loading
QA Contact: esther → stephend
Comment 3•23 years ago
|
||
can you post some numbers your getting varada? That way we can see if the
timeline stuff is working right and if the numbers make sense. I'm particularly
interested in seeing something like clicking on several messages of roughly the
same size and making sure the reset timer stuff is working (same for the folder
pane)
469Kb message - three tries for accuracy - 1.583,1.572 and 1.582 seconds.
Comment 6•23 years ago
|
||
sr=mscott then. thanks guys.
Checking for pref before using timeline to prevent being called in regular
builds.
Attachment #59356 -
Attachment is obsolete: true
Comment 9•23 years ago
|
||
Comment on attachment 62542 [details] [diff] [review]
Adding pref check for timeline
sr=mscott but you should add this pref to mailnews.js and default it to false.
Then remove the try / catch around your pref reading code since it should never
return an error if you define a default value.
do you want to be disabling the timing code in nsMsgStatusFeedback if this pref
is set as well?
Attachment #62542 -
Flags: superreview+
Reporter | ||
Comment 10•23 years ago
|
||
Adding the mailnews.timeline_is_enabled pref to mailnews.js: default is false.
Reporter | ||
Comment 11•23 years ago
|
||
The code in nsMsgStatusFeedback neednt be checked with the pref because they
wont be built without the timeline environment whereas we should safeguard JS
which is present always.
Status: NEW → ASSIGNED
Comment 12•23 years ago
|
||
Comment on attachment 62559 [details] [diff] [review]
adding pref for timeline measurement in mail
sr=mscott
Attachment #62559 -
Flags: superreview+
Comment 13•22 years ago
|
||
taking all of varada's bugs.
Assignee: varada → sspitzer
Status: ASSIGNED → NEW
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Updated•16 years ago
|
Assignee: mail → nobody
QA Contact: stephend → message-display
![]() |
||
Comment 14•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
![]() |
||
Comment 15•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•