Good idea. Tho in the code itself (from a cursory glance) in L141 Sequencing(...) I see a bunch of nested maps - I don't know Scala but I think this may be a pe

Good idea. Tho in the code itself (from a cursory glance) in L141 Sequencing(...) I see a bunch of nested maps - I don't know Scala but I think this may be a performance issue? Rather than hyperfocusing on parallelism or event systems etc since that stuff is comparitively hard to solve maybe refactoring this function/algo at the core of the pairing would have more bang for buck https://github.com/ornicar/lila/blob/98691c8901cc0e7d0f338f4270217c12997d139f/modules/tournament/src/main/TournamentApi.scala https://github.com/ornicar/lila/blob/98691c8901cc0e7d0f338f4...