Hi Maxim, are there any pitfalls when removing the RoomClient from the database? I will first remove it from the DB. Optimization of the session Map comes later. I will try to look into EHCache to set up a memory store later.
Sebastian ---------- Forwarded message ---------- From: SebastianWagner (JIRA) <[email protected]> Date: 2012/11/1 Subject: [jira] [Updated] (OPENMEETINGS-459) Remove RoomClient from database To: [email protected] [ https://issues.apache.org/jira/browse/OPENMEETINGS-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] SebastianWagner updated OPENMEETINGS-459: ----------------------------------------- Labels: Performance (was: ) > Remove RoomClient from database > ------------------------------- > > Key: OPENMEETINGS-459 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-459 > Project: Openmeetings > Issue Type: Bug > Components: Cluster > Affects Versions: 2.1 Apache Incubator Release > Reporter: SebastianWagner > Labels: Performance > Fix For: 2.1 Apache Incubator Release > > > Having the RoomClient in the database causes several performance issues. > RoomClient should stay in the session. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
