Are you doing anything to track and know whether the DB is the bottleneck? I'd recommend tracking heroku postgres metrics[0] in librato and try and find correlation. What DB plan are you using?
[0] https://devcenter.heroku.com/articles/heroku-postgres-metrics-logs On Wed, Mar 26, 2014 at 10:47 AM, richard schneeman <[email protected]> wrote: > If your DB is the bottleneck you can use followers and octopus to allow your > app to read from a different db than it writes to > https://devcenter.heroku.com/articles/distributing-reads-to-followers-with-octopus > this can help spread the load. > > > On Tue, Mar 25, 2014 at 8:00 PM, Robert Fletcher <[email protected]> > wrote: >> >> Rack::Attack is an interesting idea. Right now we're deploying a separate >> heroku app, but I don't much like that solution both because the database >> might be the bottleneck, and it means we have to make sure two separate apps >> stay in sync. Ideally we'd be able to deploy to one instance and handle it >> all. >> >> >> On Tue, Mar 25, 2014 at 5:56 PM, Dave Perrett <[email protected]> >> wrote: >>> >>> If you can identify the automated traffic somehow by IP/UserAgent/etc, >>> you could use https://github.com/kickstarter/rack-attack to throttle it, >>> letting regular traffic through unthrottled. It would refuse excess >>> automated requests though, which may not be what you want (?). >>> >>> If you just want a duplicate copy of the app, you should be able to point >>> both apps at the same database and run them in parallel, though this won't >>> help if the DB is the bottleneck. >>> >>> dave >>> >>> >>> On 26 March 2014 11:47, Robert Fletcher <[email protected]> wrote: >>>> >>>> We have a situation where we have traffic coming in from two sources. >>>> One is regular traffic from users, and another is data coming in from >>>> automated sources. We're running into a problem where there can >>>> occasionally >>>> be a flood of traffic from our automated endpoints that effectively DDOS's >>>> our servers. The solution we're thinking might be effective would be if we >>>> could have our automated endpoints transmit their data to a different url >>>> and have that be managed by a separate process on our Heroku instance. >>>> Something like `endpoint.ourapp.com`. We're not as concerned about >>>> responses >>>> being prompt on that side of things, though we want our web side to remain >>>> responsive for our users. Is this possible, and if so, how would we go >>>> about >>>> implementing it? Are there other alternatives that might be more effective? >>>> >>>> Thanks, >>>> - Robert >>>> >>>> -- >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Heroku" group. >>>> >>>> To unsubscribe from this group, send email to >>>> [email protected] >>>> For more options, visit this group at >>>> http://groups.google.com/group/heroku?hl=en_US?hl=en >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Heroku Community" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Heroku" group. >>> >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/heroku?hl=en_US?hl=en >>> >>> --- >>> You received this message because you are subscribed to the Google Groups >>> "Heroku Community" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> -- >> You received this message because you are subscribed to the Google >> Groups "Heroku" group. >> >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en_US?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Heroku Community" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. > > > -- > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Heroku Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
