Good point, I didn't check all the images and probably had assumed that
there was one that was huge. Another candidate to look at, is the number
of file transfer threads that her server can maintain for each client, this
is often limited. I have seen one occasion when a user cranked the number
down to just a few (2 or 3) and transfer became very slow as some transfers
had to wait on others to complete, but this was limited to pages with lots
of images.
this of course would be a server issue (apache or whatever) and not
PHP. Seems also that browser security (firewalls) could be a factor as well.
Warren Vail
warren@xxxxxxxxxxxx
At 03:14 PM 2/16/2006, Curt Zirzow wrote:
On Thu, Feb 16, 2006 at 02:39:54PM -0800, Warren Vail wrote:
> MARG's suggestion is right on,
>
> I took a look at some of the images, and while relatively small at 250 x
> 300 pixels, they end up displaying in an image statement that limits them
> to 15 x 16 pixels (or there abouts) on the finished page. If you only
need
> 15 x 16 pixels, resize the files to that size and reduce the transfer size
> to about 5 percent of their current size. What you are doing is
> transferring all the pixels then asking the browser at the destination to
> resize them. This will eat up bandwidth very fast. If you need to keep
> the original image with lots of pixels, keep copies on your work machine
> and not on the server.
Yes, this an issue, but doesn't explain why it takes 20 minutes to
load page in full, while 90% of the time is waiting for a response.
I hardly think the problem is either php or image size related,
there is something else wrong.
Curt.
--
cat .signature: No such file or directory
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
