Hi Peter,
My book does not specifically cover this. Although my first thoughts are that there two potential causes of high memory usage.
1) The large number of frameworks that Grails builds on. It uses Hibernate and Spring under the hood so loading all of these classes is going to take up some memory. For single web applications deployed to a
Tomcat server this will probably not cause issues, so long as you give the server a realistic amount of memory (512M). Deployments that require a number of Grails applications to run under one Tomcat instance may want to look at packaging the applications so they can share Spring and Hibernate libraries. This is not covered in the book.
2) Application design. If the domain objects are implemented to perform eager fetching on their relationships then you could experience memory problems as too much data is loaded on every request to the database. This is covered in the book when I talk about n+1 query performance problems.
Cheers,
Jon.
