Not an answer to the adapter issue...

If you're not married to Sinatra and you're building a largely
API-centric solution, then you might want to consider using
Goliath/EventMachine rather than Sinatra if you're aiming for
non-blocking, high-concurrency consumption of your API.

Michael
On Thu, Feb 21, 2013 at 12:30 PM, Tom Demeyer <[email protected]> wrote:
> Not neccessarily (or even likely to be) a sequel issue, but your combined
> experience may be able to point me in the right direction..
> We're writing an api based on nginx, passenger, postgres, sinatra and
> sequel.
> Everything runs fine with single requests, but as soon as I hit it with a
> buch of simultaneous requests ruby rack processes start to hit 100% cpu and
> hang.
> Running strace against these shows a continuous loop on 'close' with a bad
> file descriptor error.
> A GDB stacktrace (with ruby-gdb, pusewicz) seems to suggest that this
> happens somewhere in the sequel postgres adapter.
> Setting the passenger_max_pool_size to 1 resolves the issue, but this is of
> course not the solution..
> This has me miffed for a couple of days now, not getting anywhere.
> Any ideas?? Postgres configuration? Setting Sinatra :lock doesn't do
> anything to help.
>
> thanks!
> tom.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sequel-talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/sequel-talk?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



-- 
http://codeconnoisseur.org

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sequel-talk?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to