why is it so darned slow?

David Schuetz dschuetz at access.digex.net
Wed Dec 13 06:13:00 PST 1995


Several comments:
	*	Can't get rid of "old" processes in Process window.
	*	Can't save search panel to local file.  Red error message  
comes up, but can't scroll to read full message.
	*	Would like also to save results of search in a local file.
	*	Some frames don't produce scrollbars when their contents are  
too large for the frame. -- http://www.nerdworld.com/users/dstein/nw102.html.   
Also don't have prev. or next. arrows within this page set.
	*	When adding to the bookmark list, could we add below the  
currently selected link?
	*	How about a click combination to open link in a new window?
	*	Should the "permanent" frames be dropped when you leave the  
site?  Or something like that? Maybe each frame should have its own prev/next  
controls, so you can keep smaller frames around when you navigate in  
subsidiary windows, but lose the frames altogether when you navigate in the  
main window?
	*	Seems REALLY slow.  What happened to viewing the images as  
they load--I get the little empty boxes, then once the .gifs turn from  
"Waiting for response" to "reading data" I get big empty boxes, but I thought  
I would be seeing the gifs fill up as they download.  Also, this seems to slow  
my entire machine down.  Anyway to reduce the priority or something? (aside  
from me running nice...)  Seems that the browser window should have priority  
over the background gif transfer, so I can at least scroll and read with  
impunity....
	*	Why can't you cache the RTF (that is, the result of the HTML  
--> SGML --> RTF sequence)?  It's really annoying to have to wait for you to  
redraw that every time, when it's in memory and should come up "instantly."   
It takes upwards of 30 seconds to simply "go back one."


Overall impressions:

It's way. Way, WAY too slow.  And I think all the slowness is in the  
HTML->SGML and SGML->RTF processing.  On a fresh instance of OW2b, I went  
right to the OW mailing list archives.  It took over 4 minutes to get through  
the HTML->SGML process--and this with me not even TOUCHING any other apps, so  
OW had most of the cycles...  Something must be broken somewhere.... [oh, and  
I use CERN locally to cache incoming pages, so modem speed wasn't a factor  
here...]

However, it's also WAY cool.  I love all the new features, but when choosing  
between feeping creaturitis and speed, I'm afraid the speed will have to win  
out.  'Course, I could always go back to lynx, but let's not get ridiculous...



david.


More information about the OmniWeb-l mailing list