Re: 8198888: Reduce string allocation churninInvokerBytecodeGenerator

2018-03-01 Thread mandy chung
On 3/1/18 12:56 PM, Claes Redestad wrote: yes, for the startup metrics I'm concerned with then a single element implementation is even ever so slightly better: http://cr.openjdk.java.net/~redestad/819/jdk.01/ Looks good to me. Mandy

Re: 8198888: Reduce string allocation churninInvokerBytecodeGenerator

2018-03-01 Thread Claes Redestad
Hi, On 2018-03-01 20:45, Bernd Eckenfels wrote: Cool, the lastClass varient then is pretty tempting (and I wont fix the multi-slot Version below, it misses a „lastUsedSlot“ field) yes, for the startup metrics I'm concerned with then a single element implementation is even ever so slightly

Re: 8198888: Reduce string allocation churninInvokerBytecodeGenerator

2018-03-01 Thread Bernd Eckenfels
usecases mid term. Gruss Bernd -- http://bernd.eckenfels.net Von: Claes Redestad Gesendet: Donnerstag, 1. März 2018 20:05 An: core-libs-dev@openjdk.java.net; e...@zusammenkunft.net Betreff: Re: 819: Reduce string allocation churninInvokerBytecodeGenerator Hi Bernd, to dispel your concerns