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
Lift
Home
+ new post
About this group
Join this group
Message from discussion High cpu load and comet (latency)
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
 
Antonio Salazar Cardozo  
View profile  
 More options Oct 14 2012, 3:30 pm
From: Antonio Salazar Cardozo <savedfastc...@gmail.com>
Date: Sun, 14 Oct 2012 12:30:31 -0700 (PDT)
Local: Sun, Oct 14 2012 3:30 pm
Subject: Re: High cpu load and comet (latency)
Print | View thread | Show original | Report this message | Find messages by this author

Long-running comet requests are not a problem, they're the system
functioning correctly. A comet request should last up to 120 seconds. If
your request is taking 40 seconds, that means it takes 40 seconds for the
comet actor on the server to send something to the client, which is
perfectly normal. Now, if you're expecting updates more frequently, it's
more likely that the load the backend is causing isn't allowing the comet
actors to actually run, so they don't get a chance to send their responses
back down to the client.

To be sure of what exactly is going on, however, we'd need to see it in
action.
See https://www.assembla.com/spaces/liftweb/wiki/Posting_example_code for
more. Also consider using a profiler like VisualVM or YourKit to get an
inner look at what exactly is taking up CPU time and such.
Thanks,
Antonio

On Sunday, October 14, 2012 6:41:31 AM UTC-4, Alexander Bertram wrote:

> Hi,

> I develop an application where I use Akka-actors ant Lift. The backend
> causes high cpu load (> 95%). I use comet actors to update the frontend.
> When I start the application, it works as expected. But after a while
> frontend update frequency decreases. At the end it won't be updated at all.
> The backend works as expected.

> After 6 minutes uptime a comet request takes up to 40 seconds (according
> to Chrome Developer Tools).

> Is there something I can do?

> Alex


 
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.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google