similar to: Spawn mongrel on demand

Displaying 20 results from an estimated 2000 matches similar to: "Spawn mongrel on demand"

2006 May 28
5
Rails, ActionController::Base.allow_concurrency and mongrel
Hello all, Are you aware of the rails ActionController::Base.allow_concurrency option ? If this option is true, rails is able to process simultaneous multiples actions. It appears that rails is thread-safe (if the user application is), and that this option is mostly unknown. Webrick take care of this option in rails-1.1.2/lib/webrick_server.rb at line 80 : REQUEST_MUTEX.lock unless
2006 Jun 05
3
Mongrel Pre-Release 0.3.13 -- Katana Suicide Concurrency
We are *days* away from the official 0.3.13 release, which will be followed quickly by 0.4 code named Enterprisey Edition 1.2. This latest pre-release update closes off the last of the annoying bugs, and adds one very nasty feature people should check out before we release. Read about Katanas below. ** This release doesn''t have win32 yet. That''ll be uploaded Monday. ** WHAT
2006 Jun 20
1
Performance tweak when local files are not served by mongrel
Hello Zed ! I''ve experimented a simple but limited performance tweak in the mongrel rails loader. With the following apache 2.2 mod proxy loadbalancer setup : # Redirect all non-static requests to cluster RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ balancer://mongrel_cluster%{REQUEST_URI} [P,QSA,L] We can assume that mongrel is called only when the
2006 Jun 15
4
Mongrel 0.3.13 Pre-Release -- Caulking Release
Hello Everyone, Francois Simond inadvertently found a way to replicate a rare but deadly bug right as I was working up the official release of Mongrel 0.3.13. This bug only happened to a few people, but thanks to the wonderful fuzzing tool Apache Bench[1] he could replicate the slow select starvation people were seeing. TESTING This bug is now fixed in the current pre-release, and I''d
2006 Jun 15
1
Performance leak with concurrent requests on static files (Rails)
Hi, I just found something weird for mongrel with static files. Performance endlessly decreases if mongrel serve static files from simultaneous requests : Here is the test setup: Ruby on Rails Mongrel (tested with 1.3.12.4 and 1.3.13-pre installed today) Ubuntu dapper, compiled ruby 1.8.4. http client : while true; do ab -n 1000 -c 30 http://localhost:3000/ 2>/dev/null | grep
2006 Mar 16
10
Substruct Open Source E-Commerce Platform
Finally it''s here :) The Rails app to do battle with the likes of Miva Merchant and OS Commerce! I''m releasing Substruct 0.051 into the wild. More information here: http://dev.subimage.com/projects/substruct Please check it out! I''d love to hear all of your thoughts - and I''m looking for contributors! -- seth at subimage interactive
2014 Mar 21
1
rsync triggers oomkiller
I added a subject so we can track this message on the list easier. ;) On Fri, Mar 21, 2014 at 12:19 PM, John Doe <jdmls at yahoo.com> wrote: > Hey, > > kernel: rsync invoked oom-killer: gfp_mask=0x200da, order=0, oom_adj=0, > oom_score_adj=0 > ... > kernel: Out of memory: Kill process 27974 (mysqld) score 361 or > sacrifice child > kernel: Killed process
2006 May 31
8
New Rails site... RightCart.com
Hello Everyone ! Wanted to announce the launch of a new, 100%, Ruby/Rails based shopping system. http://www.rightcart.com (our blog: http://www.rightcartblog.com) It''s basically a shopping widget that allows users to make purchases directly through the widget.... no need to be redirected to a third party shopping cart. You can sell anything you want by upload the products onto the
2019 May 23
2
system unresponsive
On Wed, May 22, 2019 at 10:02 AM mark <m.roth at 5-cent.us> wrote: > That seems unlikely. Foe one, I've seen that... but I *always* see entries > in the log about the oom-killer being invoked. For another, this isn't a > compute node, it's *only* a fileserver, serving projects, home > directories, and backups (home-grown b/u, uses rsync), and backups don't >
2011 Sep 05
5
Bug#640500: xen-hypervisor-4.0-amd64: xend invokes oomkiller and reboots machine when creating DomU's
Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: normal Tags: upstream When creating Xen DomU's, at some point xend invokes the oom-killer and the entire machine restarts: Sep 5 12:04:59 arbiter kernel: [259697.101212] __ratelimit: 136 callbacks suppressed Sep 5 12:04:59 arbiter kernel: [259697.101218] xend invoked oom-killer: gfp_mask=0x200da, order=0, oom_adj=0 Sep 5
2007 Apr 03
3
MediaTemple Image upload
Hi All, I''m hosting with MediaTemple who are currently using 0.3.3 of mongrel on their GridServer. My rails app has an image upload facility whereby if you upload a large image (e.g. 5Mb) mongrel crashes. I''ve requested an upgrade to the latest version of mongrel but don''t believe that''s going to happen too soon. I''m not getting too much
2010 Jul 26
8
Why does my DomU keep going mad?
Hi All, I''ve got a DomU that sometimes goes mad. I can''t ssh or usually even console to it. The time I did manage to console I got a load of dumps about being out of memory and swap, but couldn''t run any commands to find out which process had gone mad :( From Dom0 I can see the DomU at 100% CPU and can only stop it with a destroy. What can I do/check to find
2006 Apr 21
1
Simple debugging solution for RJS templates
I know I love the new RJS templates but the one annoying thing is that I don''t get the nice Rails error pages anymore when something goes wrong. I wrote up an article with a code snippet for fixing that. Hopefully it will help out some of those as frustrated as I was. http://www.height1percent.com/articles/2006/04/21/improving-debugging-for-ajax-and-rjs -- Posted via
2019 May 22
2
system unresponsive
Out of memory? We?ve definitely seen similar symptoms (it?s been a while, so I?m not sure they were identical) for compute nodes running large memory jobs. Noam
2009 Jan 07
2
R "Threatens" SAS According to The NYT
On Wed, Jan 7, 2009 at 11:05 AM, ajay ohri <ajayohri at yahoo.com> wrote: > > FYI..not a R -Help Topic, buy I dont know which list to post discussions like this. > Regards, > Ajay > > ---------- Forwarded message ---------- > From: ajay ohri <ajayohri at yahoo.com> > Date: Wed, Jan 7, 2009 at 10:46 AM > Subject: Re: R "Threatens" SAS, According to
2017 Jul 26
8
[PATCH 0/3] Kconfig dependencies: acpi-video, backlight and thermal
Hi everyone, It took me a while to figure this out properly, as I kept getting circular or missing dependencies with video drivers. This set of three patches should simplify the situation a bit, mostly by cleaning up the dependencies around CONFIG_ACPI_VIDEO. With all three patches applied, I no longer run into those related warnings. If everyone agrees on the general direction, I hope we can
2008 Jan 25
4
ferret success stories?
Hi all, there was a recent thread[1] on rails-deploy about Ferret in which a lot of people complained of problems using it in production. I''ve been using Ferret (with DRb) for many months now with no serious issues. I''m assuming the posters know what they''re doing so I''m guessing they''re just using Ferret in higher-scale environments than me. I
2008 Jan 22
9
Cannot connect when spawning new workers on demand
Hi! I''m using the latest&greatest backgroundrb with rails 2.0.2 on ubuntu dapper. I''ve made an app that lets you run a query on several servers at once, which are selected at runtime. Therefore, for each server that is selected, I spawn a new worker and assign its work. After everything is completed, the workers are deleted. I often get this error:
2006 Jun 20
18
RE: [PATCH] Blktap: Userspace file-based image support.(RFC)
> AW> This should be fixable though. I''m also not sure how carefully > AW> dm-u watches block completion responses to ensure safety of > AW> metadata updates relative to data writes. This too should be > AW> fixable -- i just don''t know if the user-level tools can currently > AW> request completion notifications on requests that they''ve
2006 Mar 23
0
Spawn-fcgi spawning & killing
While we were trying out a new capistrano setup tonight we noticed that the spawner would alternately spawn fcgi processes, then the next time it would kill them, then create, then kill, etc... >From everything I can see/read/know, spawn-fcgi should not affect running processes, right? Anyone else see this weird behavior? For now we are using the ''check the port before