New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: CWD-466
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Justen Stepka [Atlassian]
Reporter: Steve Smith [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Crowd

Storing login tokens in an external DB is inefficient

Created: 02/Aug/07 07:40 PM   Updated: 31/Jan/08 11:27 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3

Time Tracking:
Original Estimate: Not Specified
Remaining Estimate: 0 minutes
Time Spent - 1 week, 1 day
Time Spent: 1 week, 1 day
Time Spent - 1 week, 1 day

Participants: David O'Flynn [Atlassian], Graham Bakay, Justen Stepka [Atlassian] and Steve Smith [Atlassian]
Since last comment: 30 weeks ago
Resolution Date: 31/Jan/08 11:27 PM
Labels:


 Description  « Hide
Currently Crowd login session tokens are stored in the primary DB (in our case postgres). However the usage patterns of the updates and deletes on these do not suit an ACID database, and frequent reindexes are required to stop perfomance degradation. Over time this can cause long delays during authentication. More information here.

As this is volatile data it would be better stored in a Crowd-local cache, preferably disk-backed. This would improve overall performance both for authentication and for other DB apps.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Graham Bakay added a comment - 27/Nov/07 04:15 PM
Before tearing the session tokens out of the DB, you need to consider how clustering would be implemented. Currently, we are depending on the tokens being in the DB, which set to replicate to each DB instance (both the Crowd app and the DB backend are clustered).

Justen Stepka [Atlassian] added a comment - 27/Nov/07 04:42 PM
Grapham,

We have considered this and plan to make this a configuration option when enabled. With our 1.3 release we are going to put some additional attention towards improving clustering.

Regards,

Justen


David O'Flynn [Atlassian] added a comment - 31/Jan/08 11:27 PM
We may yet decide to rejig the locations of the UI in the Administration section.