[Tickets #13463] Re: Horde_Core-2.13.1 breaks SQL database access

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/13463
------------------------------------------------------------------------------
  Ticket             | 13463
  Updated By         | arjen+horde at de-korte.org
  Summary            | Horde_Core-2.13.1 breaks SQL database access
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


arjen+horde at de-korte.org (2014-09-05 11:08) wrote:

> I know that the performance is worse with SQL Session Handler but we  
> have Horde installed in two diffent systems and if we use Standard  
> PHP Session files we have locking problems, and we haven't been able  
> of getting the "Distribute Cache Table" option to work.

If you manage to setup a Distributed Hashtable and use it for session  
storage, you'll probably find that in some cases it will perform worse  
than the SQL sessionhandler. If you update the calender view in  
Kronolith for instance, in Firefox up to six listEvent processes will  
run concurrently. But since they will all try to lock the session at  
the same time and have identical backoff intervals, it will require at  
least 500 ms before they finish. The SQL sessionhandler will run these  
processes in parallel, without having to wait for a lock. In my  
system, the SQL session handler is noticeably faster.

See also http://bugs.horde.org/ticket/13231