[Tickets #8563] Performance issues with Horde Routes

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8563
------------------------------------------------------------------------------
  Ticket             | 8563
  Created By         | fabio.bacigalupo at gmail.com
  Summary            | Performance issues with Horde Routes
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Enhancement
  State              | New
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


fabio.bacigalupo at gmail.com (2009-09-08 13:31) wrote:

We are experiencing performance issues with Horde Routes (version  
0.4). We are using HR as part of the Seagull framework where the Horde  
Routes package is integrated very nicely.

We have around 200 rules for Horde Routes to process. If I test with  
just one rule the function _createGens() takes 0,16ms. With 50 active  
rules the function takes around 18ms to pass. With all of them active  
the same function in Horde/Routes/Mapper.php takes a bit more than  
1000ms on every page request to execute. It seems there is a  
correlation between the number of rules and the execution time which  
increases drastically on every rule added after a certain point.

It's no surprise looking at the code of _createGens() which iterates  
through the list of rules three times.

A possible solution is to cache the entire "$gendict" in Mapper.php  
(~line 330-380) after it is first generated.

This ticket is a follow-up to a conversation [1],[2] held on the dev list.

[1] http://lists.horde.org/archives/dev/Week-of-Mon-20090817/024285.html
[2] http://lists.horde.org/archives/dev/Week-of-Mon-20090824/024313.html