Issue Details (XML | Word | Printable)

Key: GLASSFISH-16852
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: oleksiys
Reporter: Scott Oaks
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

[PERF] Large performance regression from grizzly character conversion

Created: 13/Jun/11 10:07 AM   Updated: 03/Dec/12 11:08 PM   Resolved: 13/Dec/11 01:45 PM
Component/s: grizzly-kernel
Affects Version/s: 4.0
Fix Version/s: 4.0_b14

Time Tracking:
Not Specified

Issue Links:
Dependency
 

Tags: 3_1-next 3_1_1-scrubbed 3_1_x-exclude PSRBUG
Participants: oleksiys and Scott Oaks


 Description  « Hide

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).



oleksiys added a comment - 13/Dec/11 01:45 PM

fixed


oleksiys added a comment - 15/Jun/11 02:20 AM

we created and fixed grizzly issue
http://java.net/jira/browse/GRIZZLY-1027

will mark this issue as fixed with the next grizzly integration