Incidently, the \"Processing took XX.XXXX seconds\" note at the bottom of a CMON page is not the time it takes the page to load, but the time it takes the server to process and execute the PHP code before displaying the results. More specifically, it only shows the time it takes that section of code which is placed between the start of the timing session and the point where \"processing took...\" is printed. Thus depending on where it\'s placed on the page, it could be skipping some sections of the code, such as the headers, etc.
Actual page load time is always longer, depending on connection speed.
When my site was on Host Department (spits!), my processing time was typically 0.2 to 0.5 seconds (sometimes higher, sometimes MUCH higher, heh, and that was when the site was up -- just don\'t use Host Department EVER). The same site on a dedicated server (my site and one other site, actually) with the same code now means a processing time of less than 0.03 seconds.
Anyway, that was a long way of saying that the quality of the server can definitely have an impact on processing times. For most sites, a difference between 0.02 and 0.5 is meaningless, but in CMON\'s case, sorting through 50k worth of images is certainly going to be a resource drain no matter what -- those small differences will add up VERY quickly. What I\'m curious about is if they\'re being stored in some massive folder or if they\'re actually being saved in an mySQL table.
Honestly, I think for performance reasons archiving of some sort is going to be a necessity sooner or later. That, or splitting things up across multiple servers -- backbone of the site on one, images on another, forums on another, etc.
Kep