We have discussed this in the last Backporters meeting, and we decided not to accept this, as a simple performance bug, which is not what the backport pocket is intended for (that's more about new features).
We have discussed this in the last Backporters meeting, and we decided not to accept this, as a simple performance bug, which is not what the backport pocket is intended for (that's more about new features).