There are currently some efficiency issues concerning the Script Registry when met with a large JIRA instance with a big stockpile of scripts. First and foremost, with a lot of scripts, the Script Registry has a problem loading up in a reasonable amount of time.
The user that brought brought light to this issue suggested a couple of changes that may help to alleviate the problem:
The biggest issue is that active and inactive workflows are shown on one page. It would already clean up A LOT if inactive workflows could be filtered out. Is that something that you could implement? (The workaround for us is to delete them manually .. but deleting workflows is not really user friendly in Jira, and we like to keep a backup copy whenever making a change).
Maybe also workflows could collapse by default, and uncollapsed manually, to keep the initial page compact.
The basic problem is that there are cases in which the Registry can't handle loading in all of the scripts and so it may be helpful to split the loading process and give the ability to filter out certain contexts that you aren't wanting to view at that moment.