:
directive correctly in the config file and also supports rolling
restarts.
/EOF
--
Eric Wong
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
was submitted by Eden Li here:
http://rubyforge.org/pipermail/mongrel-users/2006-October/001845.html
This patch was accepted by Zed Shaw here:
http://rubyforge.org/pipermail/mongrel-users/2006-October/001847.html
--
Eric Wong
improve it).
[1] yes, I realize that saying that the number of 10s responses have
dropped is like saying we've won the Special Olympics :)
--
Eric Wong
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman
process far more difficult as I require Mongrel to accept connections
haproxy didn't forward; so I disabled concurrency on the Mongrel
side instead.
--
Eric Wong
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman
in any Unixy environment... I have no idea on
whether Windows implements something similar to Process.getpgid, or
for that matter, anything on Windows' process management.
Process.kill(0, pid) also works and is (in my experience) more
widely used.
--
Eric Wong
--
Eric Wong
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
running
on 1.9 yet (and nothing in production on 1.8, either, yet).
Let me know if there are any optimizations/bugfixes in particular I can
help with, too.
--
Eric Wong
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org
://repo.or.cz/unicorn.git (mirror)
http://repo.or.cz/r/unicorn.git (mirror)
Have fun!
--
Eric Wong
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
in this thread here:
http://groups.google.com/group/rack-devel/browse_thread/thread/5e5b52892f5e9353
--
Eric Wong
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
or Hash instead. I can't
remember exactly what's wrong with them, even, but
they were BAD.
finalizers - make sure the blocks you pass to them don't have
the object you're finalizing bound to them, a common
mistake.
--
Eric Wong
://zbatery.bogomip.org/ (no, not a typo :)
[3] http://unicorn.bogomips.org/
[4] http://rainbows.rubyforge.org/Rainbows/ThreadSpawn.html
/shameless plug(s)
--
Eric Wong
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman
if it's all on the same box.
With TCP, you should also check to see you have enough local ports
available if you're hitting extremely high (and probably unrealistic :)
request rates.
--
Eric Wong
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
12 matches
Mail list logo