Re: Using SQl to store aspx pages and memory problems
- From: "TJS" <nospam@xxxxxxxx>
- Date: Sat, 2 Jul 2005 14:23:23 -0700
what exactly does this mean ?
"as each page is requested it is retrieved from SQL saved to the
temp directory and compiled "
why are you saving it twice ?
if it 's saved in sql why not just write it back to the client?
"matvdl" <matvdl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:753E0555-B034-40F7-BD3A-E3EE61600EA0@xxxxxxxxxxxxxxxx
>I have a system that was originally developed in asp - the pages are saved
>in
> SQL (there are over 10,000 pages) and saved to a temp directory in the
> server
> when requested by a client.
>
> I have updated this system and changed the pages that are saved to the
> server as aspx - everything works fine and pages can be served - but
>
> Its not impossible for a single client to request 100 plus pages in one
> session - as each page is requested it is retrieved from SQL saved to the
> temp directory and compiled - problems are.
> - Performance is well down on the original asp system - I believe that
> this due to the compiling of the pages in asp.net
> - The memory usage of server also goes through the roof - there is a
> considerable increase in memory as each page is loaded
>
> Are there any solutions to these problems??
>
> --
> matthew
.
- Follow-Ups:
- References:
- Using SQl to store aspx pages and memory problems
- From: matvdl
- Using SQl to store aspx pages and memory problems
- Prev by Date: Re: Reference repeater data
- Next by Date: horzontal looper how in vb.net
- Previous by thread: Using SQl to store aspx pages and memory problems
- Next by thread: Re: Using SQl to store aspx pages and memory problems
- Index(es):
Relevant Pages
|
