As I have been looking forward to these performance improvements since
about june/july here is my opinion:
"What performance improvement would justify movement of net poller into C
The to-be-expected performance improvement, which I think is substancial,
justifies such a pragmatic move. The conceptual issues could be fixed in
the next-following release, building hooks into the runtime so other Go
programs can benefit by using a standard interface to gain the same
advantage; my feeling is that there will not be enough time to do THAT by
year end (I could be wrong).
There is the issue the higher conceptual cause, like writing more key
portions of Go in Go and therefore not in C. Thats a very fine and
respectable goal, however from my experience in software, users will see
the actual results and performance increase more, and see less the fact
that something is done in a conceptual optimal or correct way. It is a
good idea and usually acceptable to be pragmatic whereever it is justified
by a substancial win in performance and therefore having more happy users.
On Thursday, November 22, 2012 6:07:46 AM UTC+1, Dmitry Vyukov wrote:
Isn't it too late to commit significant scheduler changes? If no, what
is approx deadline before Go1.1? If yes, will it be possible to
release the scheduler changes before Go1.2 (I guess another year)?
What performance improvement would justify movement of net poller into