Currently I don't have the breakdown for this; I will make some measurements and will post the breakdown soon. Socket communication may not be slow but the number of calls made via JSSh seems to be the main cause of the slowness. The logic for selecting an element makes number of calls depending upon the number of elements on the page. One thing that I did is that I wrote the entire logic of locating an element using _javascript_ and then sent this entire _javascript_ fragment to JSSh in one single call. This enhanced the performance by almost 10 - 15X but its still slower than IE :-(.
So, I think it is the number of calls that are made to the JSSh is causing the problem.
Regards,
Angrez
On 9/8/06, Andrew McFarlane <
[EMAIL PROTECTED]
> wrote:
Do you have a breakdown as to the amount of time spent in each phase of this communcation cycle? Socket communication isn't inherently slow, so what is the "slow piece" here?
Andrew
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.openqa.org/thread.jspa?threadID=3448&messageID=11015#11015
_______________________________________________
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
_______________________________________________ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
