Hi! Seems to be similar as we are experiencing here:
Switching back to 4.2.0 fixed this performance issue: