abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ant elder (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ABDERA-277) Excessive calls to flush() on the Writer responsible for writing JSONStream data.-
Date Thu, 06 Jan 2011 19:58:45 GMT

    [ https://issues.apache.org/jira/browse/ABDERA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978479#action_12978479

ant elder commented on ABDERA-277:

Patch applied, thanks for the fix Olve.
I'll give it a day or two to see if any other Abdera devs have any comments but if not then
I'll do a 1.1.2 release to include the fix. 

> Excessive calls to flush() on the Writer responsible for writing JSONStream data.-
> ----------------------------------------------------------------------------------
>                 Key: ABDERA-277
>                 URL: https://issues.apache.org/jira/browse/ABDERA-277
>             Project: Abdera
>          Issue Type: Bug
>    Affects Versions: 0.4.0, 1.0, 1.1, 1.1.1
>         Environment: Seen on Jetty7 and in local unit-tests.
>            Reporter: Olve Sæther Hansen
>            Priority: Critical
>         Attachments: Removed_unnecessary_calls_to_flush()_on_the_Writer_instance_writing_the_JSONStream_.patch
> When I am creating a feed with a lot of entries, say 2-3000, the JSON serialization is
horribly slow. XML serialisation is very fast in comparison.
> I am using Abdera together with Jersey, via Jersey integration. 
> Using curl and Jersey content-negotiation the xml-file downloaded instantely. The json-file
took as much as a minute and a half, and as little as 22 seconds. 
> Some investigation lead me to the excessive calls to flush in the JSONStream-class.
> https://github.com/apache/abdera/blob/abdera-1.1.1/extensions/json/src/main/java/org/apache/abdera/ext/json/JSONStream.java
> My proposal for a fix is in the attatched patch.
> I hope someone can put this in as soon as possible. I will have to make a local "fork"
for this fix until it is released through proper channels. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message