search for: num_processors

Rails instances themselves are almost always single-threaded, whereas Mongrel, and it''s acceptor, are multithreaded. In a situation with long-running Rails pages this presents a problem for mod_proxy_balancer. If num_processors is greater than 1 ( default: 950 ), then Mongrel will gladly accept incoming requests and queue them if its rails instance is currently busy. So even though there are non-busy mongrel instances, a busy one can accept a new request and queue it behind a long-running request. I tried setting...

...to daemonize. here is my configurator block:: config = Mongrel::Configurator.new(:host => OPTIONS[:ip]) do #debug(''/gateway.rb'',[:access,:threads]) listener :port => OPTIONS[:port] do uri("/gateway.rb", :handler => RUBYAMF::MongrelServlet.new, :num_processors => OPTIONS[:processors]) end run.join if OPTIONS[:daemon] daemonize end end Any ideas? Also I was looking in the mongrel source and see that in the daemonize method your calling Daemon.daemonize. Is that depending on some library? I don''t see it anywhere in the...

...r whatever coordination type */ - firstcpu = first_cpu(cpufreq_dom->map); + firstcpu = cpumask_first(cpufreq_dom->map); if ((perf->domain_info.coord_type != processor_pminfo[firstcpu]->perf.domain_info.coord_type) || (perf->domain_info.num_processors != @@ -181,11 +186,18 @@ int cpufreq_add_cpu(unsigned int cpu) goto err0; } + if (!zalloc_cpumask_var(&policy->cpus)) { + xfree(policy); + ret = -ENOMEM; + goto err0; + } + policy->cpu = cpu; per_cpu(...

I''ve checked in a patch that will hopefully fix ''acpi=off'' and ''acpi=ht'' modes for domain0. It''s been tested on just one machine so far, so it''d be good to get some wider feedback. :-) -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...ut I think maybe some of you hit this problem and solved it somehow. Another issue: on my system, mongrel_rails --version Mongrel Web Server 1.1.3 (installed as a gem) the --num-procs parameter does not seem to work. To debug the problem I added STDERR.puts "TEST: #{worker_list.length} #{@num_processors}" on line 279 of /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb, and to my surprise it looks like the parameter is ignored. If I run it $ mongrel_rails start -a 127.0.0.1 -p 8999 --num-procs 1 & [1] 18617 ** Starting Mongrel listening at 127.0.0.1:8999 ** Starting Rails with de...

Hi, Is there any documentation on enabling hypervisor support for both C and P-state control? On xen-unstable and linux-2.6.18-xen.hg, if I enable cpuidle=1 on the xen command line and then run xenpm, I will get output for C-states (shown below) but it complains that "Xen cpufreq is not enabled!" cpu id : 0 total C-states : 2 idle time(ms) : 73264 C0

Hello! Run problems after upgrading to mongrel 1.0.3 from 1.0.1: # uname -sr FreeBSD 7.0-BETA1 # mongrel_rails start ** Starting Mongrel listening at :3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload

...zero_port_fix 2007-08-05 15:29:23.000000000 -0700 @@ -560,7 +560,7 @@ @socket = TCPServer.new(host, port) @classifier = URIClassifier.new @host = host - @port = port + @port = @socket.addr[1] @workers = ThreadGroup.new @timeout = timeout @num_processors = num_processors

...tion -d -a 127.0.0.1 -p 6833 -G config/mongrel.yml Which also worked, and generated a YAML file with my options: --- :cwd: /home/mcornick/rails/mcornick.org/current :includes: - mongrel :environment: production :timeout: 0 :log_file: log/mongrel.log :config_script: #:pid_file: log/mongrel.pid :num_processors: 1024 :debug: false :group: :docroot: public :user: :host: 127.0.0.1 :mime_map: :port: "6833" :daemon: true And it almost works. If I then try: $ mongrel_rails start -C /home/mcornick/rails/mcornick.org/current/config/mongrel.yml ** You have sendfile installed, will use that to serve...

...ad_mostly def_to_bigsmp = 0; +unsigned long __read_mostly mp_lapic_addr; /* Processor that is doing the boot up */ -unsigned int boot_cpu_physical_apicid = -1U; +unsigned int __read_mostly boot_cpu_physical_apicid = BAD_APICID; + /* Internal processor count */ static unsigned int __devinitdata num_processors; @@ -89,18 +83,9 @@ static int __init mpf_checksum(unsigned return sum & 0xFF; } -/* - * Have to match translation table entries to main table entries by counter - * hence the mpc_record variable .... can''t see a less disgusting way of - * doing this .... - */ - -static int mpc...

...files: !ruby/object:Mongrel::DirHandler default_content_type: application/octet-stream index_html: index.html listing_allowed: false path: / guard: !ruby/object:Mutex {} klass: !ruby/object:Module {} listener: *id001 death_time: 60 host: 0.0.0.0 num_processors: 1073741823 port: "3001" socket: !ruby/object:TCPServer {} timeout: 0 workers: !ruby/object:ThreadGroup {} What''s weird is that i can go to: http://localhost:3001/config/resources and see the erb template output with <% .. %>. Currently I am running Mongrel 0.3.20 but i...

I''ve posted this to rails-deployment as well. I have to administer a medium size rails app (1''5 million requests each day), recently I''ve switched from lighttpd + fcgi to apache + mongrel. In the following lines I am going to describe the platform: All machines are running Debian Etch, with 4 gb ram and dual core intel32 processors. Web server runs debian''s

...wait until a slow Rails action has finished before they can run. If another Mongrel in the pool becomes free, then the requests that got queued behind a still-busy Mongrel would still be stuck and unable to get to the free Mongrel. Disabling concurrency on the Rails Mongrel (with "num_processors: 1" in the config)[1] will cause clients to be rejected outright and users will see 502 (Bad Gateway) errors. Bad Gateway errors getting returned to clients are bad, a slightly slower site is still better than a broken site. The developers also lack the resources to migrate to thre...

Hello All, Yet another release of Mongrel proudly pushed out for everyone to review and comment on. This time though, I''ve done up a little website that''s *way* better than the plan Rdoc that used to stand in for the site like a one-legged leper. * http://mongrel.rubyforge.net/ As you should already know, Mongrel is a fast HTTP server and library for Ruby partially written in

On Wed, 15 Jun 2011 14:17:28 +1000 Stephen Rothwell wrote: > Hi all, > > Changes since 20110614: on x86_64: arch/x86/xen/mmu.c: In function 'xen_flush_tlb_others': arch/x86/xen/mmu.c:1234: error: 'num_processors' undeclared (first use in this function) kernel .config file is attached. (CONFIG_SMP is not enabled.) --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -------------- next part -------------- A non-text attachment was scrubbed... Name: config-r8110 Type...

...s mongrel::start -h to get help. I''m using sudo above to replicate monit, not because I run Mongrel as root. Here''s Mongrel''s config file: $ cat /usr/local/www/xltester.com/config/mongrel.yml --- :environment: production :host: 127.0.0.1 :config_file: :group: xltester :num_processors: 1024 :docroot: /usr/local/www/xltester.com/public :port: "4785" :prefix: :mime_map: :cwd: /usr/local/www/xltester.com :debug: false :daemon: true :log_file: /usr/local/www/xltester.com/log/mongrel.log :includes: - mongrel :user: xltester :pid_file: /usr/local/www/xltester.com/log/mongrel...

...#continue with aliases for static content ProxyPass / http://localhost:8000/ ProxyPassReverse / http://localhost:8000/ ProxyPreserveHost on </VirtualHost> mongrel.yml: --- :host: 127.0.0.1 :throttle: 0 :includes: :docroot: public :debug: false :mime_map: :port: 8000 :timeout: 60 :num_processors: :config_script: :daemon: true :group: adam :environment: development :pid_file: log/mongrel.pid :cwd: /usr/home/user/myserver :prefix: :user: user :group: user :log_file: log/mongrel.log when I use x_send_file with the following in one of my rails controllers: x_send_file(@order.file_name, :typ...

On Wed, 15 Jun 2011 14:17:28 +1000 Stephen Rothwell wrote: > Hi all, > > Changes since 20110614: on x86_64: arch/x86/xen/mmu.c: In function 'xen_flush_tlb_others': arch/x86/xen/mmu.c:1234: error: 'num_processors' undeclared (first use in this function) kernel .config file is attached. (CONFIG_SMP is not enabled.) --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -------------- next part -------------- A non-text attachment was scrubbed... Name: config-r8110 Type...

On Wed, 15 Jun 2011 14:17:28 +1000 Stephen Rothwell wrote: > Hi all, > > Changes since 20110614: on x86_64: arch/x86/xen/mmu.c: In function 'xen_flush_tlb_others': arch/x86/xen/mmu.c:1234: error: 'num_processors' undeclared (first use in this function) kernel .config file is attached. (CONFIG_SMP is not enabled.) --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -------------- next part -------------- A non-text attachment was scrubbed... Name: config-r8110 Type...

...s generated in the config file: --- :user: mongrel :host: 0.0.0.0 :mime_map: :prefix: :port: "3000" :daemon: true :cwd: /srv/www/railsapps/myapp :includes: - mongrel :environment: production :group: webdev :log_file: log/mongrel.log :timeout: 0 :config_script: :pid_file: log/mongrel.pid :num_processors: 1024 :debug: false :docroot: public i then run mongrel_rails start -C config/mongrel.conf and mongrel start, but the pid file is still not written. the log directory perms are 775 and owned by group webdev. in addition the mogrel.log file is being written. verfied this on 2 separate systems....