Comments on: Catalyst vs Rails Round Two

By: c9s

c9s — Tue, 21 Jun 2011 11:23:10 +0000

by using Perl5.10 + Feersum + Plack,

you can reach more than 15000+ requests per sec.

By: davewood

davewood — Tue, 09 Nov 2010 09:30:33 +0000

Currently fastcgi with apache seems to be the most recommended deployment method for catalyst.

Alternatives:
- nginx
- lighttpd
- apache(mode_perl, fastcgi)
- IIS
- LiteSpeed
- Starman

http://wiki.catalystframework.org/wiki/deployment

By: Mathieu

Mathieu — Fri, 13 Nov 2009 20:11:54 +0000

how do you deploy your applications ?
mod_perl for catalyst ?
passenger for rails ?

and you should not compile ruby with -O3, -OS is better. there are some articles about that around the net.

and I believe MRI != 1.9, you can’t call 1.9 MRI.

By: Caleb Cushing ( xenoterracide )

Caleb Cushing ( xenoterracide ) — Sat, 24 Oct 2009 10:10:53 +0000

Any Chance you’d throw some benchmarks of django up? and maybe one of the php frameworks?

By: victori

victori — Mon, 31 Aug 2009 20:24:40 +0000

@Ted

Sorry for the late response…

1. config.threadsafe! is enabled and jruby-rack is configured for a single runtime.

2. I use jetty as our production and test container. It handles requests concurrently due to config.threadsafe being enabled.

Hope that helps.

By: Tex

Tex — Mon, 24 Aug 2009 10:02:18 +0000

Hi, very interesting article.

I have a question: when you refer to JRuby Multi-Threaded what do you mean ? config.thread_safe! enabled on config/environments/production.rb or something else ?

I’m wondering how to handle concurrent requests on rails 2.3.x using JRuby on Glassfish Gem, using Mongrel Java and so on but without results…

Example:

rails concurrent
cd concurrent
script/generate controller test test

edit app/controllers/test.rb

class TestController < ApplicationController
def test
sleep 10
@value = Time.now
end
end

edit app/views/test/test.test.html.erb

edit config/database.yml

production:
adapter: jdbcsqlite3
database: db/production.sqlite3
pool: 5
timeout: 5000

Now launch glassfish gem in production mode:

jruby -S glassfish -e production -n 4 –runtimes-min 4 –runtimes-max 4

Now try (concurrently) get 4 times the page:

http://localhost:3000/test/test

I receive the results queued (the last result after 40 seconds) this happens for glassfish gem, webrick, mongrel…

How can I handle concurrent requests under jruby/rails ?

By: Radu B.

Radu B. — Fri, 17 Jul 2009 16:02:27 +0000

Where is django in the new benchmark?
I really think it could be very interesting to know the difference…

By: Nilson Santos F. Jr.

Nilson Santos F. Jr. — Wed, 01 Jul 2009 16:31:14 +0000

I think Nateware comment is extremely unhelpful to the passerby as he lists his frustrations with two other technologies *unrelated* to Catalyst.

Neither FormBuilder nor SQL::Abstract are parts of Catalyst. As a matter of fact, FormBuilder isn’t even a recommended option at this point.

By: john napiorkowski

john napiorkowski — Thu, 28 May 2009 17:03:26 +0000

I’m sorry you had such a bad experience with Catalyst, however you may not have dug so deeply since SQL::Abstract is used not in Catalyst but in DBIx::Class (a pure Perl ORM) and FormBuilder is a completely separate project. You’re confusion is reasonable, since many people contribute to both DBIx::Class and Catalyst and a lot of the examples floating around do use both.

Formbuilder is probably not the recommended system at this time.

Since I don’t know what you were trying to do, I really can’t offer any suggestions. I have the opposite experience from you. I pulled my hair out trying to make Rails do what I needed. I find Rails seems to be fine for brand new project with no legacy code, since you have to restrict yourself very heavily to the Rails Cool Aid to get the benefits. But when I need to integrate legacy databases, or have databases with multi field primary / foreign keys, etc. I just didn’t enjoy it. Again, it might be a personality thing as well, programming languages fit people like gloves.

By: Nateware

Nateware — Thu, 14 May 2009 03:05:17 +0000

Yeah, but this benchmark misses the point that Catalyst still sucks.

We tried to develop in it, since mod_perl screams and I contributed FormBuilder and SQL::Abstract which are heavily used within Catalyst. It was a horrible experience which I’ve tried to wipe from my memory at all costs.

When we switched to Rails, my stress level decreased by dramatically, and our app performs quite well.

The database is always the bottleneck anyways.