Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
carrierwave
Home
+ new post
About this group
Join this group
Serious drag on JSON rendering
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Micah Alcorn  
View profile  
 More options Feb 7, 4:14 pm
From: Micah Alcorn <ad...@micahalcorn.com>
Date: Tue, 7 Feb 2012 13:14:06 -0800 (PST)
Local: Tues, Feb 7 2012 4:14 pm
Subject: Serious drag on JSON rendering
Print | Individual message | Show original | Report this message | Find messages by this author
I have two applications where JSON is rendered by a Rails API for use
on a mobile client. Both apps use CarrierWave 0.5.8 with Rails 3.1+
and Fog to connect to Rackspace Cloud Files. One uses mongoid and the
other activerecord.

In both cases, if my controller retrieves an array and renders HTML,
there is no problem. But if I render JSON and the model includes a CW
attachment, the rendering is exponentially slower. For example, my
User has many Photos, each containing an Image (CW). If
@current_user.photos.count == 13, then the Rails default JSON render
will take about ninety (90) seconds! Rendering HTML might take three
(3) seconds.

However, if I use json_builder and do not include Image object, then
JSON rendering takes approximately the same amount of time as HTML.
Then I have to reconstruct the Image urls manually on the client side,
which is don't think is a good long term solution.

Is this normal, or am I missing something? Thanks!


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Daniel Doubrovkine  
View profile  
 More options Feb 9, 12:10 am
From: Daniel Doubrovkine <dbl...@dblock.org>
Date: Thu, 9 Feb 2012 00:10:18 -0500
Local: Thurs, Feb 9 2012 12:10 am
Subject: Re: [CarrierWave] Serious drag on JSON rendering
Print | Individual message | Show original | Report this message | Find messages by this author

You're probably hitting Fog and then Rackspace to figure out an URL or
something like that. It will take some debugging - we had one of our
functions on the image uploader calling something in Carrierwave that
resulted in a remote call.

--

dB. | Moscow - Geneva - Seattle - New York
dblock.org <http://www.dblock.org> -
@dblockdotorg<http://twitter.com/#!/dblockdotorg>


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google