Re:The Only Reason My App Worked Was Due to a Slow Database
by tbrownaw on Tuesday April 10, 2012 @01:57PM
(#3823475)
So... what, the client had a polling loop with no delay other than the time to actually make the ajax request?
[ Parent
| on HN ]
Re:The Only Reason My App Worked Was Due to a Slow Database
by jv22222 on Tuesday April 10, 2012 @02:11PM
(#3823545)
The client makes a lot of ajax requests since it's so ajax heavy and there is no throttling on the concurrency. When 5-10 requests hit the server from the same client at the same time it is a "little" bit like a dos attack.
Re:The Only Reason My App Worked Was Due to a Slow Database
by jv22222 on Tuesday April 10, 2012 @02:39PM
(#3823697)
@jonknee - It's true there could be less. That's a future optimization. Here's the type of requests that are happening...
ajax/get-accounts
ajax/get-streams
ajax/get-other-settings
ajax/store-client-view
ajax/get-tweets
ajax/sync-relationships
Re:The Only Reason My App Worked Was Due to a Slow Database
by mapgrep on Tuesday April 10, 2012 @04:28PM
(#3824237)
Any idea why that's pegging the CPU? My naive analysis would be that once the database has sent/stored the data, the server is just doing some light filtering/serialization and sending it off to the client. But obviously there's more going on if these requests (en masse) can get you to 100 load.
Shot in the dark: Is there some kind of sorting going on?