13653 - Investigate news message display performance.

Status: RESOLVED WORKSFORME

(MailNews Core :: Backend, defect, P3)

Description

[(not reading, please use [e-mail] instead)]

I know of a couple ways I can speed this up.
this is a place holder bug for now.

Comment 1

[(not reading, please use [e-mail] instead)]

marking m11, accepting

Comment 2

[leger]

Putting on [Perf] radar.

Comment 3

[(not reading, please use [e-mail] instead)]

add [PERFORMANCE]  to summary

Comment 4

[lchiang]

Due to all-hands Tuesday 21st, build smoke tests may not be run

Comment 5

[lchiang]

oops. Wrong pasted comment earlier. Should be:
(target milestone is M11 or M12 - add to mail beta tracking bug)

Comment 6

[Phil Peterson]

M15. It's fast enough, considering that we don't have an NNTP connection cache.

Comment 7

[leger]

Bulk add of "perf" to new keyword field.  This will replace the [PERF] we were
using in the Status Summary field.

Comment 8

[(not reading, please use [e-mail] instead)]

moving to m16.

Comment 9

[selmer (gone)]

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.

Comment 10

[scottputterman]

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.

Comment 11

[Arthur]

Cc'ing myself.

Comment 12

[guanxi]

A 4 year old bug that never had any development activity ... sayonara

Comment 13

[Stephen Donner [:stephend] Not actively reading bugmail]

>------- 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.

Comment 14

[David :Bienvenu]

we have an nntp connection cache now - marking wfm.