Yea, what clinched it for me was when loading a template from disk took longer than it took to spin up a new instance of my app. A dead giveaway, if ever there was one :)
Someone at google backported the current Go template library to the version of Go running on Appengine, and it supports multiple templates in one file, if you want to go that way, itll be only one network read per instance (per file). Since I was minifying anyways, and had a foo.template and a minified version named foo.min.template, it made sense for me to switch to a model with a foo.template and a foo.template.go. In the go file, I just have the minified template as a string literal. Since this is compiled into the binary, no file access! For people who dont have a distinct minify step, maybe the multiple templates in a file option is the way to go. But I highly recommend having a minify step for all of your html, css, and js anyways, it can save you a significant amount of time from startup, and will save you and your users some bandwidth Sanjay -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/LHwRhGODEDcJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
