@sivy LOL! :) No, the overhead of firing up a Ruby interpreter and loading up the libraries is at least a half second anyway. The rest is likely just I/O and string processing. This is the curse of static site generation.
@donmelton@sivy In my first real developer job, we had a content generator that worked on the same principle. It was Classic ASP building the site navigation around static content. Custom templates and all the fun stuff. I'd forgotten all about it.