If everyone feels that there may be risks with inline, can we add a separate inline test in ci? Or even release a separate inline jar specifically for daily SNAPSHOT preview versions. We can even write a test in downstream projects such as pekko-http to test the performance difference between inline and regular versions. The main problem now is that we can only prove that there are no problems with the parts covered by our tests, but we really have no way to prove that there are no problems with the parts not covered by our tests :(
- Re: Inliner results for Pekko Http + Dedicated HW for b... Johannes Rudolph
- Re: Inliner results for Pekko Http + Dedicated HW ... Matthew de Detrich
- Re: Inliner results for Pekko Http + Dedicated... Johannes Rudolph
- Re: Inliner results for Pekko Http + Dedic... Matthew de Detrich
- Re: Inliner results for Pekko Http + D... Johannes Rudolph
- Re: Inliner results for Pekko Htt... PJ Fanning
- Re: Inliner results for Pekko... Matthew de Detrich
- Re: Inliner results for Pekko... Matthew de Detrich
- Re: Inliner results for Pekko... kerr
- Re: Inliner results for Pekko... Matthew de Detrich
- Re: Inliner results for Pekko... kerr
- Re: Inliner results for Pekko... Matthew de Detrich
- Re: Inliner results for Pekko... PJ Fanning
- Re: Inliner results for Pekko... Matthew de Detrich
- Re: Inliner results for Pekko Htt... Matthew de Detrich