Ha. Yeah, my guess is it can do a lot better than that!
I realized I was risking running abreast of the Rails scaling debate, but it’s important to realize that in our case, it wasn’t really about whether Rails could handle the volume, but more what we wanted to achieve from a UI standpoint client side.
In other words, it had a lot more to do with *how* we were choosing to use Rails. I suspect there would be an argument to make in favor of HTML streaming/pushstate, etc. It was really just the direction we chose to go that meant Rails as we were using it started to break down.