Hi Guys,
We are experiencing the same issue - spy will identify a java element within a couple seconds locally, but on our VM runtime resources it stretches to 8-10 seconds. We end up increasing the timeouts on our waits just to prevent exceptions. I know the java automation guide suggests tricks like reversing the tree or removing intelligent waits (definitely do not want to move to dumb waits), but I would like to know if any of you have found a setting on VMs to give them the same performance as we see on physical machines? We tried different versions of java, more RAM and CPU, but only saw an improvement of about a second per spy.
Thanks,
Tyler