So, here's the article on installing the Mysql gem on OS/X. I had to
monkey patch mysql.c, and then it worked after that.
http://blog.maxdunn.com/articles/2006/12/12/installing-mysql-gem-on-
mac-os-x-10-4
Thanks for the tip Luis. We'll see if this improves the resource
drain I've been seeing.
Yeah, that part where I said HTTP, I meant TCP/IP. With my latest
project it's all been HTTP, so they're starting to seem a little
interchangeable. Shame on me :-)
Thanks,
Pete
On Sep 12, 2007, at 3:30 PM, Nathan Vack wrote:
On Sep 12, 2007, at 4:57 PM, Luis Lavena wrote:
What db engine/adapter are you using? Maybe mongrel is trying to
close
pending connections left in the limbo (from HTTP serving or db
connections).
I'm using the compiled mysql gem 2.7, connecting to localhost over
TCP. Web-side, I'm using mod_proxy and mod_rewrite -- yeah, I'm
proxying on my development box.
I don't think it's waiting to close HTTP connections, as the service
never becomes unresponsive, and I'm only running one mongrel. Perhaps
the database disconnect call sometimes thrashes?
FWIW, I'm on an Intel (Core 2 Duo) mac. It only eats CPU on one core.
Mysql version is 5.0.21 -- the precompiled one from mysql.org.
And... I doubt *anyone* is connecting to a mysql server over http ;-)
-Nate
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users
