Closed
Bug 13653
Opened 25 years ago
Closed 17 years ago
Investigate news message display performance.
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
Future
People
(Reporter: sspitzer, Unassigned)
References
Details
(Keywords: perf)
I know of a couple ways I can speed this up.
this is a place holder bug for now.
Reporter | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M11
Reporter | ||
Comment 1•25 years ago
|
||
marking m11, accepting
Summary: [PERFORMANCE] investigate news message display performance. → Investigate news message display performance.
Whiteboard: [Perf]
Reporter | ||
Updated•25 years ago
|
Summary: Investigate news message display performance. → [PERFORMANCE] Investigate news message display performance.
Reporter | ||
Comment 3•25 years ago
|
||
add [PERFORMANCE] to summary
oops. Wrong pasted comment earlier. Should be:
(target milestone is M11 or M12 - add to mail beta tracking bug)
Updated•25 years ago
|
Target Milestone: M11 → M15
Comment 6•25 years ago
|
||
M15. It's fast enough, considering that we don't have an NNTP connection cache.
Bulk add of "perf" to new keyword field. This will replace the [PERF] we were
using in the Status Summary field.
Updated•25 years ago
|
Summary: [PERFORMANCE] Investigate news message display performance. → Investigate news message display performance.
Whiteboard: [Perf]
Comment 9•25 years ago
|
||
Triage to M17. Please add beta2 keyword if this must make beta2. Please let me
know if this must be done by M16 feature freeze.
Target Milestone: M16 → M17
Comment 10•25 years ago
|
||
moving to future milestone. We are going to investigate mail message performance
which will probably affect this bug but we aren't going to investigate news
performance specifically.
Target Milestone: M17 → Future
Comment 11•24 years ago
|
||
Cc'ing myself.
Comment 12•21 years ago
|
||
A 4 year old bug that never had any development activity ... sayonara
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
>------- Additional Comment #12 From guanxi 2003-11-04 19:26 -------
>
>A 4 year old bug that never had any development activity ... sayonara
So? And that was justification for killing it?
I'm reopening this, Seth or mscott or bienvenu can kill it again if necessary.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Updated•20 years ago
|
Product: MailNews → Core
Updated•18 years ago
|
Assignee: sspitzer → nobody
Status: REOPENED → NEW
QA Contact: stephend → backend
Comment 14•17 years ago
|
||
we have an nntp connection cache now - marking wfm.
Status: NEW → RESOLVED
Closed: 21 years ago → 17 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•