I have run tests on the file at the URL provided - it has just a few image files in the 10-70 KB range in JPEG, GIF, and PNG formats. The tests were run on the same computer (133MHz, 64M) under both '95 and NT. Here is approximate wall clock times to load the file: NT Build from December 6 seconds 95 Build from December 70 seconds Build 02/08 (today) 55 seconds Navigator 4.0 under '95 on this computer displays the file instantly and reports all the graphics files loaded in one or two seconds. '95 is obviously very sick but the poor performance on NT compared to Navigator 4.0 seems quite notable to me as well. I would appreciate knowing what you think about this problem if you could spare a moment to send me a note. Michael Leventhal CITEC email@example.com
This sounds like it is related to the cache problem in the current builds. People are currently working on the cache problem. I will keep this bug open to be sure I check it after the next iteration of netlib fixes. -pn
Just a quick note. I see a huge difference in performance between viewer and appviewer on linux. I don't have a current, unmodified build on wintel for testing. I am assuming the test was run on apprunner. Let me know if I'm wrong.. -thanks, pn
Summary: Win '95 Image Load 12X slower than NT → win95/nt image display performance regressed from 4.x display performance
My tests were run using the viewer application.
I have important new information about this bug. The performance problem only occurs when the html and graphic files are read off disk - read off the internet performance is comparable to Navigator 4.x. I repeated the test using the 2/10 build today with the same result. Under '95 approximately 55 seconds to read the file off local disk, 11 over the 'net. Under NT from local disk it is about 6 seconds. Same 133mHz, 64M machine.
Thanks, Michael. This info narrows down the problem considerably. -pn
Putting on [Perf] radar.
eli: Could you run a quick test. I think the issues for this bug have been addressed and this is now closable. -pn
Sure. Will do on Tuesday.
Okay, Wednesday. The short answer is that loading the driving.jpg image from this page after saving it locally (4.27.99 build, Win95) simply results in the chrome being replaced with random bit garbage, and doesn't actually load the image. I'll spend more time investigating this tomorrow and have useful comments back. Thanks.
So, now that we actually a *working* File/Open command, I'm no longer seeing this problem on the 4.3.99 builds (using the driving.jpg image from the user manual.) Specifically, I do note that a network image load is taking twice as long as a local load, but I can attribute this time to the fact that it redraws the chrome & sidebar upon reload. (Will write up a separate bug report for that.) firstname.lastname@example.org, are you still seeing a performance degradation on the current builds? If so, could you possibly share more of your wisdom on this issue? Thank you!
Status: ASSIGNED → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → WORKSFORME
Since no feedback received, yeah, verifying as WORKSFORME.
Since no feedback received, verifying as WORKSFORME.
You need to log in before you can comment on or make changes to this bug.