•
•
•
•
Summer is drawing to a close and many of the things which have distracted me from my blog are becoming less pressing, so it's about time for me to crank this back up — we'll have to see how well I keep up with it. Of course, there are a lot of exciting things on the horizon that are prompting me to write. One of the biggest is the release of V8, the JavaScript VM that's part of Google's Chrome.
With the recent release of JRuby 1.1 RC2 I’ve rerun my ‘Real World Performance’ benchmarks. In addition to my normal run I’ve added a second longer run, and the results surprised me. Let me tell you what I did, and then we can take a look at the results. In both cases I use an application that builds a catalog of good and bad patterns. Then it reads in syslog output and compares the log
With the release of JRuby 1.1RC1 I’ve run a new set of LogWatchR performance tests. This time, I’ve only run a set of 1.0 and 1.1 versions of JRuby. If you’re really interested in seeing more about 1.8 and 1.9 performance, you can always go look at my older post on the topic. As a bit of clarification up front, this test measures the execution time of a simple minded log analysis tool I wrote/
It looks like the JRuby guys are getting serious about running Rubinius on their platform: "I added the minimum dependencies needed to get it rbx building and running bin/ci the same with JRuby" Charles Nutter They're not all the way there yet, Charles reports that he's still hitting failure at the end of the build. It's getting closer though, and with the history of cooperation the Rubinius
Well, Ruby 1.9.0 landed yesterday, as expected. I’d be remiss if I didn’t start out by thanking matz, ko1, and all the other hackers involved in getting this milestone release out the door. It’s a great step for Ruby, and one that we’ve been waiting a long time for. The bad news is that 1.9.0 is just a development release branch leading up to 2.0, and it doesn’t yet run Rails or Mongrel.
Well, with the new versions of JRuby out, I figured it was time to fire up my LogWatchR benchmarks again. For this test I run 20 minutes worth of syslog entries from the system I work on through a log analysis tool I built in Ruby. There are about 75,000 syslog entries in there, so there’s a reasonable amount of IO to be done, not to mention a lot of regexp pattern matching to find potential
In my post on SICP 1.1.6, there were a couple of questions raised about my Ruby code. Fabio Akita Your first example would be better written off as: def abs(num) num < 0 ? -num : num end Personally, I really hate the ternary if, I’ve always thought that it makes code harder to read. It’s probably still worth looking at though, since my biases are just that. Peter Cooper ... I was just
With Ola Bini’s JRuby book out, I thought that I should take some time to talk to him about it. Read on to see what Ola has to say about JRuby, JRuby books, and other languages. You’ve written the first JRuby book. Obviously, it couldn’t cover everything, so what JRuby books are you hoping to see come out over the next year or so? Ola Well, there
Ola’s new book, Practical JRuby on Rails, is out sooner than I expected. I’m not going to write a review of it since I was a technical reviewer, but let me recommend it to you. This is the first book out there about JRuby, it’s got great coverage of integrating Ruby and Java in enterprise settings, and it’s by one of the core JRuby developers. What more could you ask for? It’s too early
The other day, Thomas Enebo and the JRuby gang cut a 1.0.1 release of JRuby and I finally got around to benchmarking it against my LogWatchR app. I used the same data set and Ruby versions as previously (I need to upgrade my 1.9.0 install to see how that work's been going, but it won't happen today). (You can see the previous version of this benchmark here.) This time around, JRuby showed
I’m a day late on this one, but the JRuby team cut their 1.0 release yesterday. This release has targeted 1.8 compatibility, and they’ve done a great job. Performance still lags a bit, but I think they’re on the right track to get things going there too. I’m looking forward to seeing what these guys pull out of their hat over the next six months. I really hope they spend more time on
Well, it’s that time again. We’ve got all the entries in for the April Blogging Contest, and another set of books to give away for May. Since this month is the target for the JRuby 1.0 release, I wanted to make sure this month’s contest reflected that. With that in mind, here’s the theme: How have you used JRuby in integrate Ruby into a Java environment?
With the new release of JRuby, I’decided to rerun my LogWatchR benchmark for ruby 1.8.5p12, ruby 1.9.0, and JRuby 0.9.9. Neither XRuby nor rubinius can run the YAML library from the Standard Library yet, so neither of them will be included in these benchmarks yet. In running this set of tests, I ran into some anomolies with last weeks data. I’ve figured it out now, and need to make a
A lot of people have jumped on the news of the JRuby 0.9.9 release, and deservedly so. This is big news for the whole Ruby community. My LogWatchR benchmark needs to be updated now that the released JRuby will run my application. This release also has all kinds of fixes, additions, and speed improvements. I think people are missing the biggest story in the announcement though:
