Auto Event Wire up is an attribute in Page directive. It is a Boolean attribute, which indicates whether the asp.net pages events are auto-wired. When we set the value of the Auto Event Wire up attribute to true, the ASP.NET runtime does not require events to specify event handlers like Page_Load or Page_Init.If we set the value of this attribute to true, framework must make a call to relate Delegate method for every Web Form (.aspx page). Therefore, it will be a performance issue and should not set the value to true if performance is a key issue.
The .NET Framework provides a run-time environment called the Common Language Runtime, which manages the execution of code and provides services that make the development process easier. Compilers and tools expose the runtime's functionality and enable you to write code that benefits from this managed execution environment. Code that you develop with a language compiler that targets the runtime is called managed code; it benefits from features such as cross-language integration, cross-language exception handling, enhanced security, versioning and deployment support, a simplified model for component interaction, and debugging and profiling services.
Pipelining is a process in which the data is accessed in a stage-by-stage process. The data is accessed in a sequence that is each stage performs an operation. If there are n numbers of stages then n number of operations is done. To increase the throughput of the processing network the pipe lining process is done. This method is adopted because the operation or the data is accessed in a sequence with a fast mode.
Storing the frequently used items in memory is referred as Caching. Caching is a used and tested technique for performance
It was a revolutionary concept that was developed by Microsoft for delivering the n-tier architecture. Later it was suffered from backward compatibility issues and then it gave birth to the .net technology, which incorporates the safer execution of code through CLR. DNA is also suffered with SIDE-BY-SIDE execution and importing and plumbing of code while executing the application into our server in asp3.0 but in .net it was completely revealed and the problem was diagnosed. DMA makes and support the two tiers and three tier to n-tier architecture application in which it can be able to communicate and transfer the data as much as it can but practically it was very difficult with "Windows DNA".
Generally, Cache is using to improve the performance of site. We have two places where we can use caching.
1. on Page Level
2. Data level Caching for saving Database hit.
As superscalar machines become more complex, the difficulties of scheduling instruction issue become more complex. Another way of looking at superscalar machines is as dynamic instruction schedulers - the hardware decides on the fly which instructions to execute in parallel, out of order, etc.
An alternative approach would be to get the compiler to do it beforehand - that is, to statically schedule execution. This is the basic concept behind Very Long Instruction Word, or VLIW machines.
There are two types of pipelines-
Instructional pipeline where different stages of an instruction fetch and execution are handled in a pipeline.
Arithmetic pipeline are different stages of an arithmetic operation are handled along the stages of a pipeline.
Each place in cache records block's tag (as well as its data) Of course, place in cache may be unoccupied, so usually place maintains valid bit so to find block in cache:
Use index of block address to determine place (or set of places)
For that (or each) place, check valid bit is set and compare tag with that of block address --- this can be done in parallel for all places in a set.
Caching can be done with so many ways like page caching, output caching etc. With ASP.NET, we can achieve this efficiently and by using CLR, which shows a direct impact on the Caching feature in .NET technology.