Php photo gallery TWG | JFUploader | TWG Flash upload | WFU | Forum

I convinced them to re-allow image.php, and they've said that as soon as they did, the load spiked again, but the interesting thing, is that they said the load spiked with requests to the cache, causing me to believe the problem truly lies with the number of images I have allowed in the index, which I believe is set to 20.

I'm thinking now that this may be the true source of the problem, as each page load by the browser would then send 20 requests to image.php, which could potentially add up quickly.

A call to image.php is completly different to a call of the cache.

image.php: the php compiler has to be started and the php files processed.
cache: The file is loaded by the webserver. Normally this is cached and very fast!

The interesting requests would the one when they allow image.php again. Because as you see on your site the gallery is almost running without it (use html mode and then even the detail pages work!).

And 20 images is of course some traffic but as you see in the speed of the gallery this is no problem at all.

But this are 20 calls to the cache - not 20 calls to image.php.

/Michael

This was their response



I requested to be able to modify it before removal, but if I can't fix it, I'm relucantly going to have to find another gallery system. Which is a shame, because I really did like this interface.

I had another thought, the folder with the bulk of the content in it named "galleries"



upon loading that page within the gallery, which it's almost assured that every load would be, since it is a random image each time, across 187 folders? As I add more folders to this list, more and more times as it's loaded, it each time loads a random image.

Would disabling this, or using a folder.png be a high speed up option?

sure - random needs a lot of calculations because the whole folder is read. But only once a session.

/Michael

I really don't think it's read once a session. While still on the same session, if I reload that page, it will load a new random image each pageload, at least I thought so in any case.

What I'm trying right now is to decrease the load time off the "gallery" section by decreasing the number of galleries shown per load. I set it enourmously high, to over 600, so that all the galleries could be shown on one page, and I've decreased that number to 6 x 3, 18.

I've also reduced the dhtml menu from 40 & 20 in ie and ff, to 10 each.

Hopefully this should be enough.

600 is a killer .

random image only loads the directory once. I get a new random image from an internal session cache because the random function is picking a random image from the images not used for random.

But as I say - you see how seldom image.php is used because the gallery is almost running without. Use the html mode - then image.php is not needed because ajax is not used.

/Michael

but I like the dhtml mode

With the settings as I have them arranged now, I was told I got the server load to very low, but he also said this, to which I don't have an answer to.



Do you know why apache connections are so high?

Each image is one connection. You do the math.

e.g. loading the main page of my demo is 74 requests.
And that are 55 images only. a couple of stylesheets and a couple of Javascripts - That's it.

Therfore it's completly normal for an image gallery.

You can save some images by removing some language flags (not all 23 are really needed)

/Michael

The guy asked why exactly each image needed it's own connection.

He showed me the top 5 apache connections,
I'm in the lead with 2041,
and the guy in second place has 2,
and third place had 1.



The guy's kinda weirded out by the high numbers.

This has nothing to do with the gallery.
This is server configuration thing:

http://linuxgazette.net/123/vishnu.html



If they configure their server right then one connection is used for several images

I only have <img> tags to get the images. This is normal html standard

But having 600 images on one page is not the problem of the gallery itself - this is a configuration thing.

/Michael

I'm currently optimizing request as last step for 1.7.
There i'll merge e.g. small css and js files that they are only loaded once.

But this will maybe be 5 or 6 requests less.

/Michael

Hey, they got that information you posted and said that there are several hundred connections that seem to never terminate:

I don't understand this because all connections to the cache are images.

and this looks e.g. like this:
<img src="./cache/01_Administration_Upload%2B-%2BTWG%2BUpload%2BFlash.gif.thumb.jpg" height="120" width="120">

And this is a normal image tag.

I cannot close anything here.

I have found something in the Ajax connections that can be closed.
I can send you this file and you can try.

/Michael

can they tell me how a request exaclty looks like?

I have checked the Ajax implementation and there a new connection is made for every request. I'm currently changing this that a connection is reused.
But this connections all go to image.php - not to the cache folder.

/Michael