mtate wrote:What is a realistic estimate on the CPU % consumed by an AJAX synchronization loop?
You're right. A DOM-based synchronization check does consume some CPU time because is has to look up the particular element/property value and compare it with what it is expected to be.
However, this is done by eValid entirely "in memory" so the overhead is very low. Our experiments suggest that fraction of CPU time consumed this way, is about 0.1%, even when the synchronization retry interval is set to 100 Hz
(10 msec intervals).
Note: This kind of sync is very fast, whereas a sync on an image value is much slower-- that's why we have a maximum 100 Hz sync rate...to assure that even that kind of sync doesn't eat more than 1% of the CPU.
Additional Note: Of all the commands that access the DOM the biggest performance hog is the
IndexFindElementEX command that searches the DOM for a match using regular expression logic. On a large and complex page, e.g.
http://www.cnn.com, it may take 1-3 seconds to search the entire page.
eValid Tech Support
by mtate » Thu Feb 16, 2012 11:43 am