-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Feb 28, 2006, at 9:12 AM, Tom Ward wrote:
On 2/28/06, Stefan Kaes <[EMAIL PROTECTED]> wrote:
Tom Ward wrote:
A second line of attack is the allows_concurrency flag itself. I
can't think when you'd ever want it to be false.
FCGI is single threaded. By having the flag, we can optimize AR for
single threaded apps.
True, but to me the existing optimization extremely premature. With
allow_concurrency = true @connection_cache is a hash of hashes, while
when false its just a single hash. The only saving (when running
single threaded) is a single hash lookup. This can't be worth the
extra complication in the code, can it?
I agree, Tom, particularly when we pay the price in brittle code.
For now, I'm removing the setting from the webrick server so folks
can continue working with trunk.
I'd like to see allow_concurrency wiped out.
Best,
jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)
iD8DBQFEBJ4QAQHALep9HFYRAsVCAJ93dpY8dOwyqypoqDyQWMw4UcSUpwCfTv5H
+B4cSCukjurm3euWZBo+8Sg=
=KNlX
-----END PGP SIGNATURE-----
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
