Rylane wrote:What's eValid's execution time footprint?
There are several factors to consider here: (1) The size of the eValid executable; (2) the initial size of eValid when it is launched; and (3) the size of the eValid in terms of memory usage after it has been running for a while.
Here's a quick rundown of each factor:
(1) The executable is about 8.3 MBytes (9.4 MBytes for the International Edition).
(2) After you launch eValid and it finishes loading the footprint is about 12 MBytes. After it reads and loads the home page (assuming it is not blank) then the footprint grows by the size of the home page.
(3) As you use eValid more and more, the internal memory grows and grows as data (including JavaScript) is stored in the local memory of the process. How fast this increases is a function of what you navigate to (how you use eValid).
The footprint growth is also a function of which version of IE you have installed on your machine. The older versions of IE tend to have a higher footprint growth, whereas the latest IE 8 and IE 9 versions have much more efficient implementations so the footprint growth is much less.
It's important to point out that the eValid footprint growth is generally LESS than the growth of the corresponding IE browser. That's because eValid, while it is a complete and fully functional browser, does not include every feature of the IE version it is launched with. Sometimes you have to accept that eValid emulates IE behavior -- both for the good and otherwise.
-eValid Support
by Rylane » Wed May 23, 2012 4:26 pm