DISQUS

@Carlos, I was in the middle of putting a wiki page together on wiki.oracle.com, but got pulled into something else. Deploying on Oracle App Server is actually pretty easy. Take a look at Warbler (it's a rubygem that allows you to easily package a rails app as a war file). Once you have a war file, you can deploy it to any java based app server.

@Laurent, I'll put some instructions and code up on Oracle Wiki soon -- probably later today tomorrow. Our original code is based on a hacked version of acts_as_authenticated. I'm going to fork a version of restful_authentication and add the Oracle SSO pieces needed for it. If you're interested, the git repo is here: http://github.com/manalang/restful-authenticati...

I'll post an entry when I've created the wiki entry on it.

@patrick, @peter, I ran my tests against a different page within the app (for some reason, AB isn't taking the cookies I pass to it so instead I'm pointing it to a page that I was able to unsecure easily). The numbers have come down quite a bit:

<pre>
Benchmarking localhost (be patient)
Finished 625 requests

Server Software: Oracle
Server Hostname: localhost
Server Port: 8888

Document Path: /feedback/new
Document Length: 6166 bytes

Concurrency Level: 4
Time taken for tests: 20.16816 seconds
Complete requests: 625
Failed requests: 513
(Connect: 0, Length: 513, Exceptions: 0)
Write errors: 0
Total transferred: 4056606 bytes
HTML transferred: 3861294 bytes
Requests per second: 31.22 [#/sec] (mean)
Time per request: 128.108 [ms] (mean)
Time per request: 32.027 [ms] (mean, across all concurrent requests)
Transfer rate: 197.88 [Kbytes/sec] received

Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.6 0 16
Processing: 35 127 119.1 105 1404
Waiting: 31 126 119.1 104 1403
Total: 35 127 119.1 105 1404

Percentage of the requests served within a certain time (ms)
50% 105
66% 122
75% 138
80% 146
90% 172
95% 266
98% 536
99% 716
100% 1404 (longest request)
</pre>

@patrick, @peter, you're right. Looks like that's a redirect. I'll test again with the redirect turned off.

Well... thanks for blowing smoke up my...

I will try to blog more often. :-)

I can't believe I held out so long (props go out to Mark Malone at Apple for pushing me over the edge). My iPod Touch has been awesome. Wifi is ubiquitous where I live. Just today, I spent the morning working at Whole Foods (where wifi is free and fast -- speedtest.net reports 4mbps down/ 256kbps up... not bad for free as in beer). Had the laptop on doing coding, while the Touch kept me up to date with email, tweets, and IM.

I'm discovering lots of cool GTD techniques too now that I have the Touch... I'll blog about that soon.

Ben, we're running goldspike with the defaults. We're not even running under JNDI yet :-)

The only real performance tweak we did was to use JRuby trunk :-). The other part is to off-load our static content to a web server that's more efficient at handling static content -- in our case, Apache -- we could have gone with Nginx, but Apache comes is already enabled with Oracle AppServer, so we used that.

I'm sure there are tons of other performance options we can enable, but for now, we're running pretty smoothly.

However, I was chatting with one of the JRuby devs today and it looks like they just found a big mem leak related to HTTP POST requests... so, you may want to wait for the official 1.1 release of JRuby.

Rich

bex, rake stats just counts the pure ruby code, irregardless of what it's running under (MRI or JRuby). It's a count of how much code we actually wrote.

We're familiar with the credo. Don't let the numbers fool you. Our controllers are actually pretty skinny (and our models are pretty fat). We just have lots of controller actions. And... to by honest, there's quite a bit of refactoring to be done.

If we ever open source the code, you'll see.

Ed, we took a snapshot of 1.1 after the performance patches went in. We're running in interpreted mode.

Wes, yes, we still dev on MRI, then test and deploy on JRuby. So, far it's working pretty well.

Charles... thx for the correction... I'm so used to working with jQuery that I treat any project with a "j" in front as "j<fill in="in" the="the" blank.="blank."></fill>

Srinivas,

I'll save all the details for another blog post, but basically, the team was comprised of me (Rich) and 4 ruby guys from ThoughtWorks. It was a fabulous team. One guy, Ola, works on jRuby core... so that helped a ton. The actual dev time actually only took about 3.5-4 weeks. The project started 6 weeks ago, but dev was compressed to a shorter time period. Development was done in an agile fashion (ThoughtWorks, defines agile).

Anyway, I'll post more details on this before the week is over.

Rich

Raimonds... absolutely. I'll be blogging more about the details after the conference is over.

Me love FriendFeed... thx for the invite Jake. Twitter rmanalan if you want an invite.

Bring back the PF keys!

FIXED!!! Thanks for reporting it!

Jake... I agree, of course. Check this out... ran into it yesterday -> Secrets to Amazon's success:

http://www.37signals.com/svn/posts/600-secrets-...

"Teams are small. They are assigned authority and empowered to solve a problem as a service in anyway they see fit.

Work from the customer backward. Focus on value you want to deliver for the customer.

Force developers to focus on value delivered to the customer instead of building technology first and then figuring how to use it..."

Hi Matt. Currently it's on a MySQL db. I will be porting it to an Oracle 10g DB and also to jRuby at some point. I wanted to get the site up and running as quickly as possible without having to deal with possible bugs I might run into with jRuby on an Oracle DB.

Fascinating stuff. After seeing Hans' demo, I tested out the software here...

http://tools.google.com/gapminder/

Tim, re: Twitter's traffic. I actually screwed up. I meant to type in 11k requests per SECOND. That's a lot.

http://www.google.com/search?q=twitter+11k+per+...

Rich

Lars, you're right... I need to define what I mean when I refer to an "enterprise app." In this case, I'm referring to the "ERP" type of enterprise app. Vendors like us, SAP, and others have typically built on a stack, whether it's proprietary or open. These are the type of pre-packaged apps I was targeting with my article.

Rich