Request for review: 6896617: Optimize sun.nio.cs.ISO_8859_1$Encode.encodeArrayLoop() on x86 (original) (raw)
Ulf Zibis Ulf.Zibis at CoSoCo.de
Sat Jan 26 03:12:38 UTC 2013
- Previous message: Request for review: 6896617: Optimize sun.nio.cs.ISO_8859_1$Encode.encodeArrayLoop() on x86
- Next message: Request for review: 6896617: Optimize sun.nio.cs.ISO_8859_1$Encode.encodeArrayLoop() on x86
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 23.01.2013 02:15, schrieb David Holmes:
On 23/01/2013 10:14 AM, Vitaly Davidovich wrote:
Personally, optimizing for interpreter (or even C1) doesn't seem worth it. If something's truly hot and best perf is desired then use C2 or tiered. If the method isn't hot enough to trigger the C2 threshold, then why bother? You're already behind the 8 ball in terms of performance. Maybe this is heresy though :). Not all platforms/products have C2.
And some people may use C1 intentionally for faster start-up.
-Ulf
- Previous message: Request for review: 6896617: Optimize sun.nio.cs.ISO_8859_1$Encode.encodeArrayLoop() on x86
- Next message: Request for review: 6896617: Optimize sun.nio.cs.ISO_8859_1$Encode.encodeArrayLoop() on x86
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]