How do you guys do it when you install Umbraco on a VPS server (Windows 2008) and are having 2 domains (2 websites) and want to conserve resource from the server. Is there any difference in theses 2 scenarios considering power pulled form the server?
1) Having 1 Umbraco installation with 1 app pool and 2 websites designed inside the same Umbraco installation
2 Having 2 Umbraco installations with 2 app pool and both sites seperated in source code and so on
Umbraco itself should have a very small footprint, so I'd say your best option would be to split it across 2 application pools.
However, if the websites have lots of common things (e.g., if they are really the same site in 2 languages), it would be best to host them in a single Umbraco instance. However, since your question was about resource management and not about reusability, the 2 application pools sounds like the way to go.
One major benefit of having 2 application pools is that if one site goes down, it will be less likely to affect the other site (high CPU or similar could still affect the other site). Another benefit is that it is less complicated to keep sites separate (e.g., you won't have to worry about Examine indexing content for both sites in the same way).
Umbraco resource management multiple websites
How do you guys do it when you install Umbraco on a VPS server (Windows 2008) and are having 2 domains (2 websites) and want to conserve resource from the server. Is there any difference in theses 2 scenarios considering power pulled form the server?
1) Having 1 Umbraco installation with 1 app pool and 2 websites designed inside the same Umbraco installation
2 Having 2 Umbraco installations with 2 app pool and both sites seperated in source code and so on
Umbraco itself should have a very small footprint, so I'd say your best option would be to split it across 2 application pools.
However, if the websites have lots of common things (e.g., if they are really the same site in 2 languages), it would be best to host them in a single Umbraco instance. However, since your question was about resource management and not about reusability, the 2 application pools sounds like the way to go.
One major benefit of having 2 application pools is that if one site goes down, it will be less likely to affect the other site (high CPU or similar could still affect the other site). Another benefit is that it is less complicated to keep sites separate (e.g., you won't have to worry about Examine indexing content for both sites in the same way).
is working on a reply...