Closed
Bug 66485
Opened 25 years ago
Closed 25 years ago
2001-01-24-mtest build response is very slow
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: fenella, Assigned: mscott)
Details
Linux (2001-01-24-13 Mtest)
Both Ninoschka and I are seeing that the branch builds on Linux and window are
very slow.
For example:
It takes 3 seconds to load a message with one line of text
Scrolling takes a few second to respond
It takes 5-7 seconds to bring up the Compose window
Closing the Compose window takes 2-3 seconds for it to disappear.
Clicking on newsgroup takes 3 seconds to load news
I have seen these problems in the trunk builds. See bug 66236.
These problem should not be in the branch build.
Comment 1•25 years ago
|
||
Fenella,
The trunk builds are really slow, but the changes that caused that aren't on the
branch. Are you sure that you weren't using the trunk?
Comment 2•25 years ago
|
||
My branch build (6.01) is running much faster than the trunk build.
Comment 3•25 years ago
|
||
Ladies,
Are you running a recommended, full, or custom installation?
| Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
| Assignee | ||
Comment 4•25 years ago
|
||
I'm pretty sure you don't have a tip build. The performance problems plaguing
the tip are not on the branch. It's running great for me.
Nothing was checked into the branch either that would have caused this.
Can you check your build dates again?
Thanks!
Scott,
yes, I have checked the build dates. It is a netscape6/6.01 build
Were you indeed using the the correct build? If not, we should mark this VERIFIED.
I showed the performance to Scott P. and compared it with Esther's machine.
This could be an isolate problem in my machine. Will investigate my machine's
performance. Verified this bug.
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•