Uwe Pross <[EMAIL PROTECTED]> writes: > Hi there, > > On 30 Apr 2003 at 17:21:52 +0200, Dominik Vogt wrote: > > > > Maybe I am a bit slow today but I don't see any coherence > > > between a couple of small image files and a performance > > > penalty (if there is such a thing). > > > > One big file = small overhead = little performance penatly > > Many small files = big overhead = ??? performance penalty > > Okay, I have thought in totaly wrong direction ;-) > > For each picture one http request and one answer is needed. > This means your computer has to send one IP packet and it > has to receive _at least_ one IP packet for each file. It > will receive propably more than one packet since if your are > on an ethernet the maximum transfer unit (MTU), which is the > maximum size of an IP packet, should be set to 1500 > bytes. This is the size which can pass the ethernet > connection directly. If the MTU is set to a larger value the > overhead is even more. > The IP4 header is between 20 (very likely) and 60 Bytes in > size, which gives a relation to the data to transmit of > about data/overhead = 75..25 on large files. The pager icons > are between 200 and 1000 Bytes in size which gives a data > overhead relation of about 50..3 (worst case - 60 Bytes > header and 200 bytes data).
In most cases, the client has the image already cached. In that case, the client (browser) sends about 550 bytes to the server. Those 550 bytes include the timestamp of the image. The server responds with about 100 bytes indicating that the timestamp hasn't changed. Thats about 650 bytes per image regardless of the image size. The slow part is not in the data itself, but in the delays between sending and receiving. > > > Have you checked the render times by using a local version > > > of the web page? You may save the web page with mozilla and > > > load it again afterwards. > > > > I'd have to learn how to set up apache first. :-( > > Not really - To check this you can store the pages and its > images with > > wget -r --level=1 --relative --no-parent \ > http://www.fvwm.org/index.php \ > http://www.fvwm.org/pictures/decorations/window_deco_simple_steelblue/ I'm not sure what you are recommending. On my mandrake system I just installed the apache rpm. It left a "httpd" daemon in /etc/rc.d/init.d. php was enabled by default. I could then access the new php pages by using file:/home/xxxx/index.php in the broswer. On my home system I don't want to run httpd by default so I just moved the httpd script to /usr/sbin. -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
