...
| Expand |
|---|
| title | Related JIRA tickets... |
|---|
|
| Jira |
|---|
| server | DuraSpace JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | filter=13612 |
|---|
| serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
|---|
|
|
Web Access Control
...
| title | Related JIRA tickets... |
|---|
| Jira |
|---|
| server | DuraSpace JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | filter= |
|---|
|
...
| 13707 | | serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
|---|
|
Performance
One of Fedora's perennial goals is "improved performance". With this as a focus, a Performance and Scalability working group [10] has progressed in the creation of repeatable, scripted tests that exercise and meter basic read/write operations. The objective of these tests is to reveal application bottlenecks and to track changes in performance as the reference Fedora implementation evolves.
...