Zed Shaw wrote:
But, why are you using ENV? You could just use any constant you want in
environment.rb. Try making a SITE_CONFIG = {'site' = 'stuff.com'} and
see if that works instead.
The reason I'm using it is because I'm running multiple sites from one
rails app. I'm trying to pass some
On Sun, 2006-09-03 at 17:45 +0200, Jeroen Houben wrote:
Zed Shaw wrote:
But, why are you using ENV? You could just use any constant you want in
environment.rb. Try making a SITE_CONFIG = {'site' = 'stuff.com'} and
see if that works instead.
The reason I'm using it is because I'm
Morning Folks,
As most of you know there were a few people who had the following three
bugs:
* CLOSE_WAIT: Lots of sockets in CLOSE_WAIT state.
* 99% CPU: Mongrel's getting stuck pegged at 99% CPU.
* LEAK: Memory leak.
I've successfully fixed these bugs or attributed them to one main cause:
I'm spending today writing documentation. I'll be updating quite a few
documents, doing some edits, and adding some user contributed docs. If
anyone has documentation suggestions, FAQ questions they'd like
included, or things they think are old and stale, then let me know.
Swing by the Lingr
On 9/3/06, Kirk Haines [EMAIL PROTECTED] wrote:
I still doubt that Mutex itself is the problem here. Sync uses the
same algorithm for exclusive locking, and I can run _millions_ of
threads through IOWA, which operates similarly to Mutex with regard to
which runs similarly to Mongrel
On Sun, 2006-09-03 at 10:42 -0600, Kirk Haines wrote:
On 9/3/06, Zed Shaw [EMAIL PROTECTED] wrote:
First, the memory leak was because of a bug in how the GC in Ruby was
collecting threads after they used a Mutex. Don't ask me why, but
switching to Sync fixed it. Problem is, this also
The company I work for is launching a new web site tomorrow.News of our launch will be published in major publications throughout the week so I want to make sure we are prepared for the load.Production Environment:
HP Proliant server w/ 8GB RAM and dual AMD64 OpteronsMemcache is used as the
On Sep 3, 2006, at 10:40 AM, Jared Brown wrote:
The company I work for is launching a new web site tomorrow.
News of our launch will be published in major publications
throughout the week so I want to make sure we are prepared for the
load.
Production Environment:
HP Proliant server w/
On Sun, 2006-09-03 at 13:40 -0400, Jared Brown wrote:
The company I work for is launching a new web site tomorrow.
News of our launch will be published in major publications throughout
the week so I want to make sure we are prepared for the load.
Freshly minted docs on that very subject:
Haha, yea tell me about it.Unfortunately this is how things have worked out.BTW: The cluster is load balanced using the mod proxy balancer in Apache 2.2.2On 9/3/06,
Zed Shaw [EMAIL PROTECTED] wrote:
On Sun, 2006-09-03 at 13:40 -0400, Jared Brown wrote: The company I work for is launching a new
So you'll be limited by what Apache will put through. Just remember too that if you're not CPU or memory bound yet, or doing as much database as possible, you can always put in more apache's and do poor man's load balancing across those with DNS.- JOn Sep 3, 2006, at 12:14 PM, Jared Brown
Hi Everyone,
Just want to get out another ping on the Mongrel pre-release saga. I've
updated a bunch of the documentation to include documents people have
donated and to beef up the FAQ for most of the questions people have
asked over the past month.
INSTALL
gem install mongrel
I want to run two or more clusters for my rails application so that I can do a seamless update and not suffer any downtime.But I don't understand how to setup two clusters since there is only one mongrel config file.
How would I go about doing this?-- Jared Brown[EMAIL PROTECTED](765) 409-08757001
On Sun, 2006-09-03 at 12:34 -0700, Zed Shaw wrote:
Hi Everyone,
Just want to get out another ping on the Mongrel pre-release saga. I've
updated a bunch of the documentation to include documents people have
donated and to beef up the FAQ for most of the questions people have
asked over the
Zed wrote:
* Using the mysql.rb instead of installing the actual mysql compiled
gem. The mysql.rb is just for development, and it sucks horribly.
Please forgive the stupid question, but how does one tell whether one is
using the mysql compiled gem or not? I've installed it, apparently
On 9/3/06, Paul Butcher [EMAIL PROTECTED] wrote:
Please forgive the stupid question, but how does one tell whether one is
using the mysql compiled gem or not? I've installed it, apparently
successfully, but I'd feel happier if I could be certain that Rails was
using it...
General procedure
Thanks Zed.On 9/3/06, Zed Shaw [EMAIL PROTECTED] wrote:
I'm spending today writing documentation.I'll be updating quite a fewdocuments, doing some edits, and adding some user contributed docs.Ifanyone has documentation suggestions, FAQ questions they'd likeincluded, or things they think are old
Try: irbirb require 'mysql'If it works, you've got the compiled version, if it throws an exception, you don't. That's how Rails itself checks for it.-- Josh H.
On 9/4/06, Jan Svitok [EMAIL PROTECTED] wrote:
On 9/3/06, Paul Butcher [EMAIL PROTECTED] wrote: Please forgive the stupid question, but
Maybe make a mention about using the mysql gem for Ruby, I noticed that right now you only have the edit to the environment.rb file up there.Also I have found this page to be infinately valuable, maybe it would be cool to through a link up for the various deployment configurations and put this one
On 9/3/06, Zed Shaw [EMAIL PROTECTED] wrote:
But, explain this:
http://pastie.caboo.se/10194
vs.
http://pastie.caboo.se/10317
First one leaks, second one doesn't (with graphs even). What's worse is
the inverse is true on win32. These scripts have no Mongrel code, no
Rails code,
On Sun, 2006-09-03 at 17:44 -0400, Jared Brown wrote:
Any estimate on when the next version of mongrel_clusters going to be
ready for primetime?
Should be ready now. It's now part of the regular Mongrel builds so you
can just get it the same way you get the mongrel pre-release.
--
Zed A.
21 matches
Mail list logo
