News for hackers. Stuff that matters.
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?

Re:The Only Reason My App Worked Was Due to a Slow Database by jonknee on Tuesday April 10, 2012 @02:34PM (#3823667)
Why are their so many requests at the same time? Can't the client make 1 request and receive back the 5-10 things it needs?