Code Forums - View Single Post

ashish · 07-21-2004, 05:59 PM

Hello all,

Here is some more information about ASP.Net

Some features of ASP.NET

Crash protection: ASP.NET has been designed to handle your memory leaks efficiently, whenever a memory leak is detected ASP.net creates another copy of itself, all new requests are directed to this new copy, the older copy is deleted along with the memory leak it created when it finishes executing the pending processes.

Memory Leaks - In order for a program to run it needs memory(RAM), after a application is terminated it should normally free up the computer memory it has been using. However it sometimes does not happen which could be due to a result of a bug/design problem in the application.

Lets say that out of 4 applications 3 fail to release all or a significant part of the memory that they were using. This memory is now tied up, now if a new application is started it could be possible that the computer does not have enough memory to provide it to run properly, resulting in a huge system slowdown or sometimes crashes.

Caching: ASP.Net allows you to build web applications that are fast, it does that by caching of compiled code, i.e. certain pages can be cached into the memory, so that they don’t take a longer time to retrieve, now the trick here is that this code is compiled, this is it is already converted into a machine readable format.

Caching/Cache MemoryIn a computer almost all of your applications and data are stored on your hard disk, whenever you access something the CPU first searches for it in the cache memory, if the data is there it is returned back the user, otherwise the CPU searches for it in the Hard disk, once the data is found it is first transported to the RAM of your system, and then from to the cache memory and then it is returned to the user.

The memory of the cache depends on the PC configuration, as more and more data is stored in the cache the previous data has to be deleted, caching makes data access faster as if the data is already stored in the cache then it cuts out the step of searching in the memory.

07-21-2004, 05:59 PM	#2 (permalink)
ashish Registered User Join Date: Jul 2004 Posts: 46	Hello all, Here is some more information about ASP.Net Some features of ASP.NET Crash protection: ASP.NET has been designed to handle your memory leaks efficiently, whenever a memory leak is detected ASP.net creates another copy of itself, all new requests are directed to this new copy, the older copy is deleted along with the memory leak it created when it finishes executing the pending processes. Memory Leaks - In order for a program to run it needs memory(RAM), after a application is terminated it should normally free up the computer memory it has been using. However it sometimes does not happen which could be due to a result of a bug/design problem in the application. Lets say that out of 4 applications 3 fail to release all or a significant part of the memory that they were using. This memory is now tied up, now if a new application is started it could be possible that the computer does not have enough memory to provide it to run properly, resulting in a huge system slowdown or sometimes crashes. Caching: ASP.Net allows you to build web applications that are fast, it does that by caching of compiled code, i.e. certain pages can be cached into the memory, so that they don’t take a longer time to retrieve, now the trick here is that this code is compiled, this is it is already converted into a machine readable format. Caching/Cache MemoryIn a computer almost all of your applications and data are stored on your hard disk, whenever you access something the CPU first searches for it in the cache memory, if the data is there it is returned back the user, otherwise the CPU searches for it in the Hard disk, once the data is found it is first transported to the RAM of your system, and then from to the cache memory and then it is returned to the user. The memory of the cache depends on the PC configuration, as more and more data is stored in the cache the previous data has to be deleted, caching makes data access faster as if the data is already stored in the cache then it cuts out the step of searching in the memory.