22-01-2013, 03:57 PM
ASP.NET Web Application
ASP.NET.doc (Size: 90.5 KB / Downloads: 23)
Web Applicationprojects are best for large ASP.NET deployments. How do they compare to Web Site projects in efficiency and layout? Here we compare the same project as a Web Application and as a Web Site project, looking into the code's internals and measuring sizes.
Binary size
When you use the precompiled site options for your Web Site project, pages are compiled into several DLLs. When you have separate files, less code can be shared between the files. This results in a higher total size of deployment. And many DLLs are slower to read in than one.
Next:What we see next here is the binary size of the deployed web project BIN folder for a deployed ASP.NET site. First, the stats for the Web Application are shown, and then the stats for the precompiled Web Site.
What the numbers indicate.
The BIN file for the Web Site contained nearly twice as much data and ten times more files. This is clearly less efficient for the footprint than the single DLL from the Web Application project. There we no inline-code pages.
Settings for the web project.
Next here are the settings for the Web Site project that were compared to the Web Application. All projects are in Release mode with no debugging enabled.
Advantages of Plastic SCM's database architecture
Plastic SCM's architecture makes it easy to configure (and switch) SQL database backends. This enables Plastic SCM to offer great scalability under heavy load and provide very efficient and safe storage. The Plastic SCM server uses a highly optimized database access layer to take advantage of each database backend.
Plastic SCM's data architecture provides:
• Proven reliability: your data is safe under all conditions.
• Well-known data backup procedures.
• Leverage for your existing investment in database systems.
• Easy integration with your existing IT infrastruture and knowledge base.
• Ability to create customized reports and dashboards, using data extracted by standard SQL queries.