Discussion: 8172978: Remove Interpreter TOS optimization (original) (raw)
Doerr, Martin martin.doerr at sap.com
Tue Feb 28 15:41:29 UTC 2017
- Previous message: Discussion: 8172978: Remove Interpreter TOS optimization
- Next message: URGENT: RFR: [BACKOUT] fix for JDK-8166188
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
It would be a success metric the other way round: If we didn't lose interpreter performance, we could have been certain not to lose startup performance.
Now, we don't know how much the impact on startup performance is. But it may be affected.
-----Original Message----- From: Aleksey Shipilev [mailto:shade at redhat.com] Sent: Dienstag, 28. Februar 2017 16:25 To: Doerr, Martin <martin.doerr at sap.com>; Max Ockner <max.ockner at oracle.com>; hotspot-dev at openjdk.java.net Subject: Re: Discussion: 8172978: Remove Interpreter TOS optimization
On 02/28/2017 04:23 PM, Doerr, Martin wrote:
The assumption behind this proposal was that interpreter performance would not suffer much on modern hardware. The -Xint benchmark is able to show that this is not true.
Ah, I see. I can't fathom why this is a success metric then.
-Aleksey
- Previous message: Discussion: 8172978: Remove Interpreter TOS optimization
- Next message: URGENT: RFR: [BACKOUT] fix for JDK-8166188
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]