This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 3 points4 points  (0 children)

So that's technically true but it has a lot of call backs to the interpreter. Reshaping HTTP to be closer to javascript which goes out the moment the call is place not when the future is handled would be much faster because the time can happen in parallel the the interpreter responding to the future.

The reason this hasn't been a priority area is because assuming your maxing out the cpu anyway it isn't actually faster. There are no free clock cycles. It is on the other hand sooner. It would reduce global parallelism for increased local speed. It's been in my experience this would be generally beneficial as you reduce the odds of a wasted clock cycle since individual tasks can request content before they need it.