Re: Using SQl to store aspx pages and memory problems

Bob,

I will respond to your response - as the designer I won’t feel as bad as TJS
who basically called me an idiot.

There are many reason why I am doing it this way - and I don't believe that
they are all stupid.

1. Firstly the system was inherited from asp - in asp this idea caused no
problems at all and worked very well - other than the overhead of obtaining
the text from SQL server and writing it to disk - it all worked very well.

2. I'm not sure - but the idea of having 10,000 aspx files sitting on the
web server does not make sense - and it would not solve my problem anyway -
the compiling time would still be there and so would the memory issues.

3. It provides an excellent mix of creating a file that has a combination
of data that was only available at the time the file was created and
combining it with functionality available at the time it was displayed.

So - the ability of me to re-design is not possible or desired – wat I have
works very well – except for the problems of memory and speed.

This was a good idea in asp - so to say that it is simply stupid when I move
to aspx is not an helpful answer and sounds more like a cop-out - what I need
is someone willing to understand the reasons for designing it this way and
for someone to attempt to answer my questions.

For example - I have saved the copy of each invoice I send out to clients as
text within a database - this text could have been saved as plain html and
forwarded to the client - but I have included a chart within these invoices
and this chart is a active x control (chart fx - fully interactive) - for the
chart fx control to display correctly it must be served from a server -
either aspx or asp page - I also need to load the control with data - so the
only way to do this was through an aspx file.

NOW - it is not possible to re-create the invoice each time someone wants to
view it - much of the data used to create the invoice is not available.

Also - the fact that SQL is involved is not the problem - the problem comes
about as a result of having 10,000 aspx files and the memory and speed that
it takes to display them.

So - can anyone help? - can anyone offer some insight into how this can be
made more efficient - is it possible to save the compiled code into the
server and load this up with the file when it is displayed. This would solve
the speed issue.

Is it possible to get a page to unload once it has been compiled - this
would solve the memory issue.

Some constructive answers would be helpful.
--
matthew


"Bob Lehmann" wrote:

> This is just such a dumb way to do things. You should just start over, and
> brain the idiot who did this to you.
>
> Bob Lehmann
>
> "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
>
>
>
.

Relevant Pages

  • Re: Memory usage and large number of pages
    ... The problem is the overhead of compiling these pages is huge - and because ... have also found that for each file that is compiled the memory increases. ... >> directory on the web server. ... >> returns the result of this page back to the client. ...
    (microsoft.public.dotnet.framework.aspnet)
  • problems with my web application
    ... my .aspx files run locally fine but when i deploy to webserver i get ... An application error occurred on the server. ... This tag should then have its ... connection string is registered in web.config. ...
    (microsoft.public.dotnet.csharp.general)
  • Page Processing
    ... I have a problem at the moment where an external program writes aspx files ... After a short time this gets out-off control and the memory of the server ... based on the code-behind class. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Using SQl to store aspx pages and memory problems
    ... Many of the pages have server side code - they are aspx files - not html ... the server and redirect the request to this file. ... written back to the client - the problem is with aspx files. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Access Denied trying to do quick editing
    ... IIS is configured to map URL to the local ASPX files via a local ... VS.Net is on a separate machine from the server and accesses the ASPX ... Then you wonder why your asp page is whacked out. ...
    (microsoft.public.inetserver.iis)