Context Navigation

Changes between Version 1 and Version 2 of Ticket #36439, comment 7

-              v1
+              v2
 > Secondly the way you're iterating over each awaitable serially in a loop prevents any concurrent scheduling execution from taking place thus you most likely wouldn't notice if the event loop was blocked as you're only processing one task at a time. You'd want to buffer up futures and await them all so they can step on each others toes a bit if you hope to catch any interference between them.
 Hello, my bad, you are right. I'm executing the code serially with awaitables. I'm putting them all into a task group, and the gap in performance is huge with a `ThreadPoolExecutor`.
+Hello, my bad, you are right. I'm executing the code serially with awaitables. I put them all into a task group, and the gap in performance is huge with a `ThreadPoolExecutor`.
 This is for 100 users only having passwords as their usernames, and I'm using the default `PBKDF2PasswordHasher` hasher. I will also check other hashers later on:
 . **Current:** 14138 function calls (14120 primitive calls) in 24.844 seconds