Agile boards may be up to 50% slower on boards with 100+ epics.

Actual behaviour

On bards that have a large number of epics (100+) agile boards may be slower up to 50% when compared to Jira 7.4.x.

On our internal tests with a board containing 320 Epics, we see following results:

Expected behaviour

Boards should be performing at least as they did in 7.4 version.

Root cause

In the development of epics in kanplan we have added epics count to allData.json request in Jira Agile. 

The code looks as follows:

ServiceOutcome<EpicData> epicDataServiceOutcome = epicsHelper.loadEpicData(user, rapidView); 
if (epicDataServiceOutcome.isValid()) { 
   workData.epicData.epicsCount = epicDataServiceOutcome.get().epics.size(); 
} 

This code is very inefficient, as creating epicDataServiceOutcome on large datasets is very expensive operation. 

Workaround

There is no possible workaround for this issue.