I haven't personally tested RoR but from a quick recall of some tests I've seen for RoR on the Web, I think our performs several times faster, and there is always room for optimization.
The point isn't if you can or not build something faster than XYZ but rather showcase that you did.
Besides that, performance of widely varying frameworks written in widely varying languages usually can't be compared in meaningful ways. It's either a micro-benchmark of a few very specific test cases (and thus, not all that useful for predicting real world performance), or it is a "real world" example, but implemented with possibly wildly divergent quality and attention to detail--if you are a Java master and you build a test app, and then do a 1-to-1 port to Python, nobody would be surprised that the Java app outperforms the Python one.
Anyway, my point is that I simply don't understand how performance could be a meaningful piece of information in this context or how being "fast" could possibly make me want to use the framework over existing frameworks. Writing it in C would be "fast"...but I wouldn't use it.
People using Java I think would be more sensitive to performance issues.
I agree that speed is not the top in the list for a framework, but having it in mind is important.
Since we know nothing about your framework, I voted "who cares?" (because I just can't take time to care about every new "framework" that comes along, even in languages I like), but if there were a, "Huh? A Java framework in 2008? How does that even happen? I didn't even know people still built websites with Java." option, I probably would have voted that way instead.