EWF - How much RAM is Enough?

  • Thread starter Thread starter Tim Houle
  • Start date Start date
T

Tim Houle

I'm using the EWF RAM component with 1 GB of RAM. I'm
using an application that utilizes a lot of RAM for image
buffering. Is there a rule of thumb when calculating how
much RAM is needed. What happens if RAM is used up and
I'm not using a page file? Is 1 GB of RAM a safe bet?

Thanks,
Tim
 
If you do not defragment system volume and do not copy or change large
amounts of data then few MB is required for RAM EWF.
Worst case scenario is that you change all clusters on disk (some full 100%
defragmentation) this would require memory that is equal to size of
protected partition.

1 GB is probably more than enough for most XPe purposes.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Tim,

Also, make sure the pagefile (if used) is not on the protected volume.

I too agree that 1 Gb should be enough for XPe usage (I'd wish for so memory :-) ) unless your embedded app(s) are not working with
disk much. E.g., database storage, though it does not make a sense to put the db storage on a protected volume.

The best answer to your question you may get testing your device in real environment 24x7. Try to stress the device (work with files
a lot) and see if EWF cache is getting overflowed..
 
Slobodan,

My image is 450MB. My application uses ~150MB - extensive
image buffering. Would I be OK with 512MB of RAM or
should I go with 1GB?
 
KM,

I'm not using a page file. However, I do have an
unprotected partition I can put it on. If I have enough
RAM, I shouldnt bother with a page file, correct? Are
there any advantages of using a page file?

-----Original Message-----
Tim,

Also, make sure the pagefile (if used) is not on the protected volume.

I too agree that 1 Gb should be enough for XPe usage
Click to expand...
(I'd wish for so memory :-) ) unless your embedded app(s)
are not working with
disk much. E.g., database storage, though it does not
Click to expand...
make a sense to put the db storage on a protected volume.
The best answer to your question you may get testing
Click to expand...
your device in real environment 24x7. Try to stress the
device (work with files
 
Hi Tim,
My image is 450MB.
Click to expand...
This is irrelevant to EWF.
My application uses ~150MB - extensive image buffering.
Click to expand...
Can you explain what do you mean by "extensive image buffering.".

If you need to write 150 MB of data to protected partition then move that
data to unprotected partition.
If you only read data, EWF will not consume memory.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
I shouldnt bother with a page file, correct?
Correct you should not bother with page file if everything is working and
you have enough memory.
Are there any advantages of using a page file?
Click to expand...
There are few minor API functions that need page file to exist so they can
report valid values. (In most cases you wont need them)

When you reserve memory with VirtualAlloc.
If you have page file memory will be reserved in page file.
If you don't have page file then whole requested memory will be allocated
(you won't be able to use it)

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Back
Top