Re: Persisting a Dataset

I'm not sure you're going to get around the memory issue without possibly
using cross-appdomain remoting because Terminal Server will create separate
app domains for each exe that is running. Also, the DataTable would have to
be read-only because I don't see how you could update the table in a
threadsafe manner through databinding. This is an interesting issue I may
have to play with. One approach could be to create a separate library with
a remotable Singleton class (inherits MarshalByRefObject) and is thread safe
which would load the table into memory and serve all the exes. I'm not sure
how the databinding would behave though. You may end up having to serialize
the DataTable across the appdomain anyways and that would defeat the
purpose.

How many TS sessions are you running? How much memory is that DataTable
actually using? You may have an easier time breaking down the amount of data
you load into the table. Does the user really need all that data available
at once? Is there a way you can fetch the data only if it is needed? If you
can store the table to disk and load it into memory only when needed, that
may be an easier solution.

"JT" <Jthayer@xxxxxxxxxxxxx> wrote in message
news:CA1CC017-8B36-4088-BA9F-A2179D895F4E@xxxxxxxxxxxxxxxx
> Hi,
> I have a Windows Forms app deployed on Terminal Server. When the app
> starts, it loads up several datatables that then serve as the datasource
> for
> comboboxes throughout the app. One of these datatables has about 5000
> ROWS,
> at 2 columns each. I would like to avoid having each user's instance of
> my
> app load such a large datatable into memory. Any suggestions on how I can
> load a globally common instance of this data, that can be used by each
> instance of my app?
> --
> John


.

Relevant Pages

  • Re: Persisting a Dataset
    ... it seems like the bulk of your memory would be taken up ... > datatable contains a list of possible medical diagnosis codes. ... >> which would load the table into memory and serve all the exes. ... One of these datatables has about 5000 ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: major iis5 asp performance problems
    ... takes to load, ... memory and dip into virtual memory, at which point hard-drive thrashes and ... is why the app gets to 50-60MB. ... >>- IIS performace tab settings ...
    (microsoft.public.inetserver.iis)
  • Re: Memory leak when using Response.Write()
    ... During work with the app this number is getting bigger to ... Then memory collection is called, ... Memory Profiler says that there is a lot of strings, ... and few DataTables and DataSets, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Persisting a Dataset
    ... > which would load the table into memory and serve all the exes. ... >> I have a Windows Forms app deployed on Terminal Server. ... One of these datatables has about 5000 ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Persisting a Dataset
    ... >> which would load the table into memory and serve all the exes. ... >>> I have a Windows Forms app deployed on Terminal Server. ... One of these datatables has about 5000 ...
    (microsoft.public.dotnet.framework.adonet)