Performance for large archives Performance for large archives
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Performance for large archives

Started by smoke10010, April 12, 2005, 10:57:33 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1
User actions

smoke10010

April 12, 2005, 10:57:33 PM
I've been doing some scouring and have noticed there are a lot of performance questions.. since I'm having the same problem I was hoping everyone would take a second and just post in here the best way to tweak their coppermine so that it loads quickly and effectively...

I know that removing the RANDOM feature for large collections will drastically increase the load time... I'm not sure about MOST VIEWED or HIGHEST RATED.. any ideas on that?...

I also removed the breadcrumb.. i'm not sure that really helped but I guess the less you use the faster..

Water-marking on-the-fly will also suck up how quickly things are done you're better off watermarking BEFORE you upload

Specifically for my site http://www.skimboarding.ca
Any ideas on how to tweak the performance up a little?

Alex
Skimboarding.ca

Joachim Müller

#1
April 14, 2005, 10:25:49 AM
on-the-fly-watermarking is the number-one culprit for bad performance; we recommend not using it at all: it just doesn't make sense if you're having much traffic.
Second thing to look into would be the meta albums (random/last uploads etc.), they eat up a lot of query time. Take a look at the debug output to see if the queries are what slows down page load. In your case, it's the sheer number of graphics on your site that makes the page load slowly. Additionally, you're using e107, which adds a lot of surplus load. In fact we don't know the e107 port (it's a user contribution) and how it works, so your question is a bit off here (we don't support ports, as we don't know the code changes that were done to make coppermine work inside the app you're using).

Joachim

smoke10010

#2
April 21, 2005, 07:51:06 PM
Yeah I've worked with both a little and e107 does contribute to slow loading as well with all the graphics and everything.. but essentially it still operates the same.. any performance tricks you use for the standalone will also work the same for the ported version from what I can tell... This post was more just to get people to post as many little performance tweaks they could come up with...


Alex
Skimboarding.ca
Print
Go Up Pages1
User actions