Are you saying that there will be 2^32 buckets will be available? If yes, we can print out the bucket id ( i know only in c++). I would take the pleasure of doing it and try to get back with results. Also, I didn't get this point of yours - "So while theoretically interesting, wouldn't it be safe in practise to consider O(1) complexity for 99.99% of cases?".

Hi @Ajinkya Can you please give a reference to "M:N scheduler" part ?

I thought C# does not require any VM. It is very interesting to know that it requires VM to run. By the way I do not know anything about C#. Iss't it a compiled language where in we can build .exe and .dlls ? As j is telling that it requires VM then I wonder what will be the format of file that we finally build to run a C# program !

Thanks.

I should take care of the way I put the words into sentences. Thanks for coming back. Anyways the questionis , for example , if I want to build a c++ application to run on Linux then I have build in in Linux machine. But in go I can do it in windows or os X or Linux. I just wanted to know if there are any other compiled languages with this feasibility.

I have a couple of questions to ask. I could google them up but anyways I will ask. Does kotlin or scala require runtime to be installed ? Are there any complied languages other than go which supports platform independent building?

When I said ' go doesn't create os threads ', I meant that it doesn't create os threads to achieve concurrency. Go routine is go's way of achieving concurrency. Ultimately it has to create a os threads. But the main thing is how many go routines are getting executed in that thread. It totally depends on what each go routine does. And thanks for info that java has something similar to nodejs's event loop. I lacked this information.

Yes, java allocates memory in heap for every object that we create. But the thread that it creates will receive a fixed amount of stack size which may not be required at all.

The previous post was between nodejs and go. I had wrong understanding of node. I though node will spwan a thread per client which is not right. But this post is between java and go. I am not conveying anything wrong here.

Most of the articles will explain event loop and event queue management of nodejs taking 'setTimeOut' (which is one of the async functions ) as an example. That makes it easy. That makes me feel like I understood it right. But, with that understanding I am not able to analyze how 100s of routes are handled be nodejs server.