...
In Review
Expand Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets resolved this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Notes
1.
...
- Announcements
- Performance Issues
- Short live transactions
- More of an impact on reads than writes, e.g. getting the root resource of your repository with 1m+ items
- Ordering adds more latency
- Ongoing work for short lived transactions
- Long lived transactions perform full join
- Short transactions perform a simpler query
- Could be expanded to writes
- Search Index
- Current work is for a synchronous update
- Question of how much of a performance impact there is when updating the index
- Possibility of adding config to update async through event bus from initial discussion
- Long running transactions in bad states
- If changes are already committed to the ocfl layer, changes can't be rolled back
- Might be able to attempt to rollback, then mark transaction as failed
- Can also prevent the transaction from being committed at all
- Migration utils
- For pid list: need to stop iterating the F3 repository once we've processed all items
- metrics: Try and capture bytes/sec
- Short live transactions
Actions
- Look through migration util commits since December to see if there are any potential causes of performance drop off.