we're having some server troubles here at antville.org today. I'm not sure what the cause is, but it's not the traffic, as far as I can tell. Rather, it looks like Helma has some trouble with garbage collection and is continously growing in size (it's taking 340MB right now, althogh the heap size should be limited to 256MB) and taking a lot of CPU time.

This may or may not be related to a problem we have with logging.

I'm not sure what to do about it. If nobody comes up with a better solution, I suggest we update to the current Helma snapshot sometime today.

In other news, /referrers is still/again slow. Maybe changing the ACCESS table didn't fare well with the existing indexes and we should remove and re-create them?

Ihr indiziert doch die einschlagenden Referrer, da geht wahrscheinlich ganz schön die Post ab, er dürfte ununterbrochen seinen Index umbauen, das saugt.

i did send details to tobi by mail. maybe you have the same problems.

you're right: memory is getting low on adele, it started to swap sometimes before (doesn't do it now). i think this definetly has to do something with the referrer-stuff (tobi is going to rebuild the indexes), and it looks like mysql still does too many full table scans ...

update: i'll start to tune mysql a bit more.

i will remove the "like" clause from the query and put the check for local referrers in logAccess(). this even will decrease the speed the ACCESS table is growing.

mysql> select count() from ACCESS where
REFERRER = "www.antville.org";
+----------+
| count() |
+----------+
|    80385 |
+----------+
1 row in set (8.00 sec)

mysql> select count() from ACCESS where REFERRER
like "%antville.org%";
+----------+
| count() |
+----------+
|   344228 |
+----------+
1 row in set (8.15 sec)

looking at these results i think we happily can get rid of these records...

robert did a great job transferring the old access table to a new one leaving away the [www.]antville.org and self-referring referrers. i removed the "like" clauses in the referrer / backlink queries and we added a regular expression match to take over their task in logAccess().

please note that this is a solution which currently only fits with antville.org's environment. that's why we did not check it into the cvs, yet (we are going to think it all over again in the next days).

any eta on when it's to be fixed?