search

localwiki / localwiki-backend-server

Primary LocalWiki backend server environment
GNU General Public License v2.0
48 stars 16 forks source link

Set up some API throttling #41

Open philipn opened 9 years ago

philipn commented 9 years ago

From @philipn on February 23, 2013 22:3

@mfb ran a script against oaklandwiki.org that threw around 100 write requests/minute and slowed the site way down. Should be an admin-configurable variable for read/writes.

Copied from original issue: localwiki/localwiki#443

philipn commented 9 years ago

From @mfb on February 23, 2013 22:7

Any idea why it slowed to a crawl? Can the site only handle 1 concurrent request?

philipn commented 9 years ago

I'm not really sure. 100 writes/minute may be too much for the setup oaklandwiki is running on. The default Ubuntu install (which oaklandwiki is running) doesn't have any caching set up out of the box. (#274)

The API hasn't been optimized yet, so this is good to watch.

philipn commented 9 years ago

Update: turns out oaklandwiki.org is on an EC2 micro instance >.< !

philipn commented 9 years ago

From @groovecoder on April 6, 2013 19:4

Is the main concern here about performance, or about API abuse?

philipn commented 9 years ago

Performance. I wouldn't really use the word abuse- sometimes people just write really crazy clients :)

We noticed that the oakland project got slammed by a single script run a while back. It was also running on an ec2 micro instance w/o caching, so that may have been a lot of it. But tastypie has throttling support so we should probably turn something on.

On Apr 6, 2013, at 12:04 PM, luke crouch notifications@github.com wrote:

Is the main concern here about performance, or about API abuse?

— Reply to this email directly or view it on GitHub.