HDonald wrote:What happens if two [or more] eValid copies try to write to a SaveRecord file at the same time?
It works.
We regularly use
SaveRecord to record intra-script timings in server loading experiments and multiple eValid instances that all are writing to the same
SaveRecord target file all work just fine.
We've even done this on "big" cloud-based machines where we have 1,000 or more BUs running and again, no problem.
The reason this is safe is that typical outputs from
SaveRecord are text strings that are one, or perhaps a few, lines. Such an output action consumes very little of the CPU and I/O resources, so even when there are 100's of such write requests at the same time the operating system is able to avoid any conflicts.
(Of course, having said that someone will SUREly come up with the counterexample!)
eValid LoadTest Support