Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. In Review

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13100
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. Tickets created this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Notes

1.

...

  1. Announcements
  2. Performance Issues
    1. Short live transactions
      1. More of an impact on reads than writes, e.g. getting the root resource of your repository with 1m+ items
      2. Ordering adds more latency
      3. Ongoing work for short lived transactions
        1. Long lived transactions perform full join
        2. Short transactions perform a simpler query
        3. Could be expanded to writes
      4. Search Index
        1. Current work is for a synchronous update
        2. Question of how much of a performance impact there is when updating the index
        3. Possibility of adding config to update async through event bus from initial discussion
    2. Long running transactions in bad states
      1. If changes are already committed to the ocfl layer, changes can't be rolled back
      2. Might be able to attempt to rollback, then mark transaction as failed
      3. Can also prevent the transaction from being committed at all
    3. Migration utils
      1. For pid list: need to stop iterating the F3 repository once we've processed all items
      2. metrics: Try and capture bytes/sec



Actions

  •  Look through migration util commits since December to see if there are any potential causes of performance drop off.