Storing login tokens in an external DB is inefficient

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • 1.3
    • Affects Version/s: None
    • Component/s: None
    • None

      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.

              Assignee:
              Justen Stepka [Atlassian]
              Reporter:
              Steve Smith (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 48h
                  48h