Quantcast
Channel: Silk Performer
Viewing all articles
Browse latest Browse all 4084

Wiki Page: Why is the fWait parameter, Minimum time or minimum mean time that this function call has to last, automatically scripted in during record?

$
0
0
When browser-level Web traffic is recorded using the SilkPerformer recorder, a wait time is included at the end of recorded functions to tell the replay engine how long to wait before executing the next function in the script. The use of wait times simulates slow connections and user processing times in order to help provide more realistic load tests. The wait time appended to a recorded function is the time elapsed between the execution of the current function and the execution of the next function. This functionality has different implications when replaying in multithread mode and in single-thread mode. For more information please see Browser-level function replay timing Note: The wait time is always zero in Stress Test mode, regardless of the values specified in the browser-level functions.

Viewing all articles
Browse latest Browse all 4084

Trending Articles