This is a silly argument. If I read you right, you are saying that a goroutine is closer to a promise&#x2F;future than a Scala actor in terms of resources used, and therefore it&#x27;s OK to use futures instead of actors in the Scala code and compare them that way.<p>That betrays the whole benchmark. The basic point of the benchmark is to answer the question, &quot;How expensive is it to create and run 1,111,111 actors in various languages?&quot; You can&#x27;t make a manual optimization that causes only 111,111 actors to be created and then say that it&#x27;s a better comparison.