Nest content areas in designs - server impact

Hi,


I was wondering what the difference is, in terms of server load, between including code directly in design assets, or using nest content areas to nest code.



For example, I have three designs for the same site, that includes a manually-controlled (as opposed to dynamic) top-level navigation. What would be the difference between putting the code directly into each design, or nesting a standard page (raw content) into the designs instead.



I'm interested in this idea to make the maintenance of the navigation a little easier, but I don't want to head down that path if it will impact on the site's performance.

In v3.8, with both design area caching and standard page caching, the overall performance hit should be minimal. However, hardcoding in the design will always be faster than a nested content, because there is zero processing requirement for the hard coded bits.