Physical and Virtual Memory

[AMDRIT]

Hello once again,

When working with objects, does .Net push any of it to virtual memory? I
know that the OS does it, I guess what I am asking is how do I claim a
portion of memory from the OS and work within that limitation?

If I were to claim 400 MB of RAM, using what, I don't know, possibly a byte
array, I would like to use that as my working limitation for data
operations. I realize that I would loose use of objects if I were to go
that route, but it seems to be the only way to limit how much memory the
application consumes while running. I also realize that .Net was geared
towards object base development, however, I cannot seem to find a reliable
way to measure my memory consumption.

There are times when I would have objects loaded in memory, and because I
would like to cache that data for possible later use, I don't release it.
When a flagged is raised that memory is nearing its limit, I would loop
through stale items and release them, and keep cutting down until I am back
in a safe margin.

Thanks in advance

[Cor Ligthert [MVP]]

AMDRIT,

AFAIK has not any current windows OS system like Unix or mainframes the
possiblitiy to limit the used memory for a task.

This option is a nice option for multiuser purpose on classic computers,
however a little bit far back in yesterday. The majority of the students in
the world have now all their own laptop.

By the way relying on information is memory is in my opinion a very unsafe
way of dataprocessing.

Just my thought,

Cor

"AMDRIT" <am****@hotmail.com> schreef in bericht
news:OQ**************@TK2MSFTNGP12.phx.gbl...

Hello once again,

When working with objects, does .Net push any of it to virtual memory? I
know that the OS does it, I guess what I am asking is how do I claim a
portion of memory from the OS and work within that limitation?

If I were to claim 400 MB of RAM, using what, I don't know, possibly a
byte array, I would like to use that as my working limitation for data
operations. I realize that I would loose use of objects if I were to go
that route, but it seems to be the only way to limit how much memory the
application consumes while running. I also realize that .Net was geared
towards object base development, however, I cannot seem to find a reliable
way to measure my memory consumption.

There are times when I would have objects loaded in memory, and because I
would like to cache that data for possible later use, I don't release it.
When a flagged is raised that memory is nearing its limit, I would loop
through stale items and release them, and keep cutting down until I am
back in a safe margin.

Thanks in advance