You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2019/10/11 19:07:27 UTC

[GitHub] [maven-surefire] Tibor17 edited a comment on issue #240: [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for remote and local process communication.

Tibor17 edited a comment on issue #240: [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for remote and local process communication.
URL: https://github.com/apache/maven-surefire/pull/240#issuecomment-541185297
 
 
   @rpdai 
   I am glad that I can talk about Netty because we need to have experienced guys and we need to finally get better progress. The reality is that the Netyy prototype [on my Github](https://github.com/Tibor17/surefire-tcp-connector) showed us that the KPI of the plugin would be sinificantly worse if we used the principal published in the prototype with Netty. Maybe i was doing something wrong but I cannot help myself. So please have a look into it and try to fix, modify it in a pull request and try to get back to our discussion in Surefire soon! It would be fansastic to get 5 millis on the startup as it is in Java. You know that there are users who really want to have a fast startup and they say in Jira that they have tests wich execution is comparable with the startup of the Jar file and forking a JVM, so we have to pay a big attention to the code and it's performance. Feel free to reply, I will be happy to see a new prototype with Netty!

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services