[Seaside] Increasing the performances of a Seaside application
stephane.ducasse at free.fr
Sun May 29 14:18:31 UTC 2011
> It's a bit better. There's no starvation if the timeout is greater than zero, but it's still a form of busy waiting, and it limits the number of queries per second per connection to at most 1000 (actually 1000 / timeout). To compare this with our native implementation - PostgresV3 - I measured 6k+ queries per second per connection and it's still not optimized for Cog (#perform: is slow on Cog).
> Thanks Levente. Unfortunatly I guess that's all we can do with a blocking FFI :(
Just that I understand why you do not have the same constraints that levente?
What are they? because he does not have either a threaded ffi.
More information about the seaside