Performance Problems with approx 2100 pics

[triadib]

Hello,

I'am running two EE's installations on my own server - one which has been stored about 200 pics and the other with about 2100 pics.
The first runs really good with best performance, the second slow down while loading one pic after another - (EE Statistics/ Photopage 5-6 seconds).

There are 15 exhibitions which are grouped, pw-protected with 3 sizes (+ thumbs and microthumbs)

I have been trying the following steps:

- more than 5 photographers in database
- more than 5 cameras in database
- more than 5 lenses in database
- more than 5 lights in database
- more than 5 categories in database
- more than 5 workflows in database
- more than 5 paths (size, thumb, microthumb) in database
- purge uncookied data
- backup the database to another, delete the original and restore to a new installed one

- modify php.ini settings to
max_execution_time = 300
max_input_time = 60
memory_limit = 16M

- modify my.cnf settings to
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
max_connections = 500
key_buffer = 32M
myisam_sort_buffer_size = 3M
join_buffer_size = 2M
read_buffer_size = 2M
sort_buffer_size = 2M
table_cache = 3000
thread_cache_size = 128
wait_timeout = 30
connect_timeout = 20
max_allowed_packet = 16M
max_connect_errors = 10
query_cache_limit = 1M
query_cache_size = 30M
query_cache_type = 1
skip-innodb

All modifications didn't bring the increasement I would expected.

The server is an INTEL-Box with 1 Proc, 512MB RAM, shared by 3 domains, PHP 4.3.11, MYSQL 4.
The table_cache parameter ist set to "YES".

Perhaps anyone here in the forum have an idea or parameter set which is useful...

Regards from Germany
Dirk

[chriz]

No ideas, sorry, but I run a server with close to 10.000 pictures on it and it runs as fast as in the beginning.
Just to let you know that the script performs well with that many pictures.

There is hope :-)
Chriz

[Pekka]

As chriz said, EE does (or should) not slow down with lots of photos. Enable debug mode, load photo page couple of times, save the output and disable debug mode. That should take about 20 seconds to do so it won't affect many visitors.

Do you see any timers on debug output which go over .1 seconds?

[triadib]

Hi,

the problem is solved.

Pekka, thanks for giving me the hint using the "debug mode" - the result showed me, that my PHP-script which I use for e-commerce caused the delay.

Now, I recoded the script and everything is fine.

Regards
Dirk