Quoting G Tellez <[EMAIL PROTECTED]>:
--> Average page response time is 8.64s. --> Average page response time is 25.1s
These times are obviously pretty terrible. In part the slowness is caused by the fact that the Links implementation currently performs lexing, parsing, type-checking (twice!) and various analyses and transformations to the program every time a page is loaded or a client-server function call is made. Caching the result of these phases should have a significant effect on performance, but we haven't treated it as a priority so far. (I've just noticed that there is actually a "cache_programs" setting which seems worth trying.)
It's not clear whether the difference between the times of the two applications is caused by the fact that one simply takes longer to type-check etc., or by Links generating inefficient queries, or by something else altogether. It shouldn't be hard to find out, though. You might start by setting the "measure_performance" flag and keeping an eye on the debug output, besides looking at the generated SQL as Ezra suggests.
Jeremy. -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ links-users mailing list [email protected] http://lists.inf.ed.ac.uk/mailman/listinfo/links-users
