Task #3177 (closed)
Opened 14 years ago
Closed 14 years ago
Decrease the frequency of `SessionCache.doUpdate` calls (sync_interval)
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-Beta4.2.1 |
| Component: | Performance | Version: | n.a. |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | 2010-10-28 (18) |
Description
omero.sessions.sync_interval=3000
configures a Quartz thread to call SessionCache.doUpdate every three seconds (though only one invocation will ever be called concurrently). This method must acquire the write lock which is an undo burden.
Change History (1)
comment:1 Changed 14 years ago by jmoore
- Resolution set to invalid
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
After thinking about this, it's not possible to just decrease the interval as a workaround, because then when an administrative update came around, methods would have to wait the 30 seconds (or whatever) until synchronization even began. It might be possible to rework SessionCache as it currently stands to use two different update threads -- one for the administrative changes (called frequently but without acquiring the write lock) and one for the forced update -- but it's probably simpler to just handle #3174 (non-blocking SessionCache). Closing.