[GLASSFISH-16852] [PERF] Large performance regression from grizzly character conversion Created: 13/Jun/11  Updated: 03/Dec/12  Resolved: 13/Dec/11

Status: Closed
Project: glassfish
Component/s: grizzly-kernel
Affects Version/s: 4.0
Fix Version/s: 4.0_b14

Type: Bug Priority: Major
Reporter: Scott Oaks Assignee: oleksiys
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
blocks GLASSFISH-16851 [PERF] Large peformance regressions i... Closed
Tags: 3_1-next, 3_1_1-scrubbed, 3_1_x-exclude, PSRBUG


In glassfish tests after moving to grizzly 2.0 (glassfish b06), we see huge performance regressions from the encoding of page results. Profiles indicated that most of this time is spent in sun.nio.cs.UTF_8.newDecoder(), which is the result of org.glassfish.grizzly.memory.HeapBuffer calling new String(byte[], int, int, Charset).

Comment by oleksiys [ 15/Jun/11 ]

we created and fixed grizzly issue

will mark this issue as fixed with the next grizzly integration

Comment by oleksiys [ 13/Dec/11 ]


Generated at Wed Mar 04 07:19:10 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.