|
hns,
April 19, 2002 at 3:19:48 PM CEST
/referrers taking too long I just noticed that the /referrers pages on Antville weblogs take forever to compute, something far beyond 5 seconds. Is there some way we can accelerate this? The easiest solution (and maybe the best one) would be to kick older records out of the ACCESS table, unless there is a reason to keep them all. Maybe it would also be possible to optimize the ACCESS table some more. Something that is definitely not very good for performance is the ... and REFERRER not like "%" + this.href() + "%" ... in the SQL query in function weblog.listReferrers_macro()...
kris,
April 19, 2002 at 3:31:15 PM CEST
btw if you think 5 seconds is too long then try manila. attention: this may additionally freeze your browser for a couple of seconds.
hns,
April 19, 2002 at 3:34:48 PM CEST
actually, my concern is not with the users waiting for the page, but with the server. Serving a page that takes more than a second to compute makes you very vulnerable to various attacks, both intentional and non-intentional.
kris,
April 19, 2002 at 3:42:44 PM CEST
i know but try the manila link. it will take more than 5 minutes. to minimize the load they actually cash the referrer page and only generate a new one if the latest version is older than an hour. ... comment
tobi,
April 19, 2002 at 5:08:19 PM CEST
sure i am happy if we could accelerate the referrers page. however, the where clause you quoted might be bad for performance but it's definitely nice for the referrers list not to get referrers from your own weblog. so, is there a different approach we could do this which is faster or is the only way dropping the "like" check? kicking out older records is what i thought of from the beginning because it was clear that the table would get enormously big very quickly. should i do this with a scheduler function?
robert,
April 22, 2002 at 2:36:11 PM CEST
maybe we should change logAccess() so that referrers from your own weblog aren't logged, then we could get rid of the "not like"-clause. and second: we could extend the auto-cleanup so that everything older than e.g. one week is deleted (the size of the access-table is getting problematic already, also because of the size of the indexes ...)
tobi,
April 22, 2002 at 2:44:12 PM CEST
doesn't the check for referrers from the same weblog at request time imply even more performance troubles? if not, i am totally +1. and +1 for auto-cleanup, too (i think this is the scheduler behind it, anyway)
kris,
April 22, 2002 at 2:51:19 PM CEST
if you delete all old entries when someone accesses the referrer page it will remain nice and small. well, given the user checks the referrers on regular basis. ... comment
|
|
The Antville Server Fund has been a great success. Thanks to everybody who contributed!
online for 8550 Days
last updated: 1/4/11, 10:22 AM  Youre not logged in ... Login
 ... home
... topics ... galleries ... Home
... Tags
... Galleries
... about antville ... download ... macros.antville.org ... help.antville.org ... translate antville! ... antville home
i understand your concerns however,
i hardly can think of a solution. certainly, if the...
by tobi (7/29/03, 9:47 AM)
Found several more similar sites
listed This is getting to be quite a concern to...
by cobalt123 (7/27/03, 7:56 PM)
Second Post Alert on Referrer
bug livecatz I put this into "help" and now here:...
by cobalt123 (7/26/03, 7:14 PM)
well it's not easy to
find from here, anyway. think we should include a link,...
by tobi (7/24/03, 11:25 AM)
clock not that it's particularly
earthshattering but the antclock is running slow by about 15...
by kohlehydrat (7/23/03, 8:25 PM)
How to log skin names
I accessed to console?? Hi, I would like to know...
by winson (7/23/03, 4:12 PM)
  powered by  |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||