Yeah. Sadly, we are all very much stuck in the YesSQL mindset (our data is relational) and would prefer to stick with that horse as long as is possible. Our performance is good right now and appears to scale to the loads we'd like to see, but since perf is typically a non-linear sort of thing regardless of what solution you use, I want to buy us as much performance with as few radical, bug-introducing changes as possible.
Tweaking two postgres parameters seems like an ideal match to that conservatism and, OK, I'll admit it, laziness. Cheers, Carson On Jan 11, 10:43 am, chris <mcclellan...@gmail.com> wrote: > Your use case (high volume, low value writes) sounds like it would be a > perfect match for one of heroku's nosql addons... mongo or couch in > particular. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
