[
https://issues.apache.org/jira/browse/SHINDIG-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Brown closed SHINDIG-479.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.0.x-incubating
1.0.0-rc1
trunk
This has been fixed for a while now. ICU still sucks, but we have the option to
skip it at least.
> Character set detection is EXPENSIVE using ICU4J.
> -------------------------------------------------
>
> Key: SHINDIG-479
> URL: https://issues.apache.org/jira/browse/SHINDIG-479
> Project: Shindig
> Issue Type: Bug
> Components: Gadget Rendering Server (Java)
> Reporter: Louis Ryan
> Assignee: Louis Ryan
> Priority: Critical
> Fix For: trunk, 1.0.0-rc1, 1.0.x-incubating
>
>
> We use the ICU4J library to detect the character set on HTTP content fetched
> from 3rd parties when the content-type header does not contain the charset.
> The code is quite expensive and the cost was also being incurred on cached
> content rewritten content i.e. basically everything that runs through Shindig.
> I've submitted a partial fix which once the charset is derived it is stored
> back into the HTTP headers so that caching and rewriting can benefit from it
> so far containers with good caching this should eliminate ~75% of the CPU
> overhead but alot of makeRequest traffic is not cacheable and suffers from
> this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
