Re: Memory usage and large number of pages



Karl,

Thanks for the response - it was helpfull.

The AJAX system looks good and I will consider using this in the future - I
have already provided similiar functionality to this by using a webservice -
this works well and I am currently looking at this as an solution to this
specific problem.

The true problem I am dealing with is actually a little more critical then
this issue - as I have been trying to discuss on another thread for some-time
- The problem I mainly have is dealing with very large numbers of files.

The main issue I have is that I have over 10,000 files - most of which
represent invoices to clients - I have to keep the original copies of each
invoice and it is not practical to re-create the invoice each time it is
viewed by the client. Currently what I do is save these files else where and
when they are requested I copy them to a temp directory on the server and
redirect the customer to the page using response.redirect.

The problem is the overhead of compiling these pages is huge - and because
there are so many there is no way to include them into the application. I
have also found that for each file that is compiled the memory increases.

Many of the files also needed to be ASPX as they have server-side logic
within them - this is used to provide a interactive charting in each invoice.

Most people have simply said that it is a bad design and I should start
again - but I can't see any other way of doing this.

What I wanted to know - is it possible to pre-compile a page somehow and
maybee save a copy of the pre-compiled class file. When the page is
requested I could copy accross a copy of this file along with the original -
when the system goes to access the file it would somehow recongize that it
has already been compiled and simply get on with processing the page. This
would mean I would need to save twice as many files - but I don't see this as
a major issue.

This solution would fix my speed issues - but does not provide an immediate
solution to the memory issue. but one thing at a time - is what I have
suggested possible????

And to extend this further - once a class has been defined - is it possible
to remove this definition - or does this definition remain available until
the process is next recycled?

--
matthew


"Karl Seguin" wrote:

> Matthew:
> Your process seems complicated. I don't know enough to say that there's a
> better way to do everything, I merely state that to indicate how hard this
> is going to be to fix things. ASP.Net will automatically recycle itself
> after it just-in-time compiles X amount of pages. From what you describe,
> it seems like every 5 seconds for every user a new page is created, forcing
> ASP.Net to have to recompile it. I would suspect that you'd quickly run
> into problems this way (however, I doubt that's, in any way, associated with
> your memory problem). Just a comment of something you should be aware of.
>
> You might want to build your entire reload/dynamic creation framework on a
> much lighterweight protocol. Again, I don't fully understand what you are
> doing, but it would seem AJAX might be able to help you here. This would
> let you asynchronously send whatever data back to your original page
> without having to reload or recreate new pages. You can learn more about
> this from: http://ajax.schwarz-interactive.de/csharpsample/default.aspx
>
> Karl
>
> --
> MY ASP.Net tutorials
> http://www.openmymind.net/ - New and Improved (yes, the popup is annoying)
> http://www.openmymind.net/faq.aspx - unofficial newsgroup FAQ (more to
> come!)
>
>
> "matvdl" <matvdl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:360563BC-3186-4455-B7A0-218D4BA0B80F@xxxxxxxxxxxxxxxx
> >I have migrated my asp application to asp.net some time ago - but I am
> >still
> > having some difficulties in understanding the best way to mange some
> > tasks.
> >
> > I currently have a page that loads a aspx web page - this page is
> > continually refreshed - every 5 seconds or so. To do this I use the
> > download
> > behavior on the client to call a particular page - say newchart.aspx. The
> > newchart.aspx than calls a custom component (vb app on another machine
> > using
> > dcom) and this app goes and creates a chartXXX.aspx file in the temp
> > directory on the web server. newchart.aspx than calls this chart123.aspx
> > and
> > returns the result of this page back to the client. chartXXX.aspx is
> > unique
> > for every call.
> >
> > On each call the memory on the server increases - until the point it
> > resets.
> > I used this method in asp extensively and never had these problems - but
> > the
> > changes in asp.net means that this is not be best way to do this.
> >
> > Can anyone suggest to me a better way of managing something like this??
> >
> > My custom app on the remote computer has the smarts of what needs to be
> > returned to the client and sometimes it simply writes a html page to the
> > temp
> > directory and this gets returned to the client - this causes no problem -
> > the
> > difficulty happens when a aspx file is written.
> >
> >
> > --
> > matthew
>
>
>
.



Relevant Pages

  • Re: Named shared memory without synchronization
    ... memory address with a single machine instruction. ... Again, if I assume an x86/x64 architecture I think i can get away with this, ... when running on a 4-way server under heavy load. ... Server runs client. ...
    (microsoft.public.vc.language)
  • Possible bug in sockets
    ... Just point the ip address of the client at the server ... The client connects 200 sockets, sends some data with each continously, ... in this scenario memory increases forever. ...
    (microsoft.public.dotnet.framework)
  • RE: Exchange 2003 and timeout errors on XP machines
    ... After replacing 1 client computer's network cable, ... Are you able to open OWA to access the e-mails on the client or server? ... Store.exe will take as much memory as possible to provide better service ... Microsoft engineers can only focus on one issue per thread. ...
    (microsoft.public.windows.server.sbs)
  • Re: Using SQl to store aspx pages and memory problems
    ... the text from SQL server and writing it to disk - it all worked very well. ... I'm not sure - but the idea of having 10,000 aspx files sitting on the ... the compiling time would still be there and so would the memory issues. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: COM server / COM client
    ... I could have written a C++ server, ... client to embed in an html page to view, insert,delete etc.. ... so we will be installing python on each. ...
    (comp.lang.python)