A look in mysql processlist shows me this :
UPDATE wp_options SET option_value = ‘a:5298:{i:1;a:2:{i:0;s:1:\”0\”;i:1;s:1:\”0\…. WHERE option_name = ‘wppa_counts_tree’
the option_value contains more than 216000 chars when I display the full update… looks a bit big !
Also found a chmod problem in my config, I don’t have the timeout anymore, but the update request is still processing in mysql, and I’m quite sure it could be useful to paginate my 6000 albums 😉
Sure I will implement pagination in album admin albums table. It is my intention always to fix capacity issues whenever they arise and whenever I am capable of fixing them. I will inform you when this works.
As long as your database accepts the 216k bytes option value for wppa_counts_tree, I suggest not to re-implement the storage method for treecounts for now. But, if this becomes a real capacity issue, i will re-implement the storage of (tree)counts.
Also look at option wppa_counts if it is not getting too big, please.
Album table pagination is now implemented in the current development version 6-5-08-006 and later.
Instructions to install: http://wppa.nl/docs-by-subject/development-version/
It will also be released by the end of this week.