Coypu VERY slow in Chrome

209 views
Skip to first unread message

Andrew Masters

unread,
Jun 3, 2013, 7:17:25 AM6/3/13
to co...@googlegroups.com
I'm seeing some very strange behaviour with Coypu in Chrome:

The following simple code runs over 100 times slower on Chrome than on Firefox:
    0.9s Firefox
1m 51.3s Chrome

Something fishy must be going on, the only difference between test runs is the Browser setting in SessionConfiguration.
I'm new to Coypu, maybe I'm missing something obvious.

I know the HTML isn't great, but that doesn't explain the difference.

Thanks,
Andy


Code:
_browser.Fillin("Your email","te...@test.com");
_browser.Fillin("Your message", "blah");


Html:
<body>

<div class="banner">
 <div class="bannerLinks">

    <div class="bannerLinksPlacement">
      <a href="/about">about</a><a href="/terms">terms</a><a href="/faq">faq</a><a href="/contact">contact</a>
    </div>

    <div class="pageLogo">
      <a href="/"><img src="/images/lantern-logo.png" alt="Lantern logo"/></a>
    </div>

    <div class="bannerLinksPlacementLeft">
    </div>

  </div>
</div>

<div class="outsideBlock">
<div class="mainBlock">

  <div class="mainBlockContainer">

  <h1>Contact us</h1>
  <form action="/contact" method="post" class="dataform"><div style="margin-top: 1em;">Your email</div><input name="username" size="24" type="text" value=""/><div style="margin-top: 1em;">Your message</div><textarea name="message" rows="3" cols="50"></textarea><div><button type="submit">Send</button></div></form>  </div>

</div>

</div>

<div class="footerSection">
    <a href="http://facebook.com/lanternapp" style="float: right; margin-top: 16px;"><img src="/images/fb.jpg" width="80px" alt="facebook"></a>
  <div class="footerLinks"></div>
    <div class="footerText" style="margin-left: 80px;">&copy; 2012 Checkin Technologies Ltd</div>
</div>


</body>

Adrian Longley

unread,
Jun 3, 2013, 7:25:09 AM6/3/13
to co...@googlegroups.com
On 3 Jun 2013, at 12:17, Andrew Masters wrote:

I'm seeing some very strange behaviour with Coypu in Chrome:

The following simple code runs over 100 times slower on Chrome than on Firefox:
    0.9s Firefox
1m 51.3s Chrome

Yes, that doesn't sound right!

Can you confirm where the majority of that time is spent:
 
Before the browser opens?
After the browser opens but before your page loads?
After the page loads but before filling in the fields?
After the fields are filled in but before the browser closes?

Might help to work out what is going on.

--
You received this message because you are subscribed to the Google Groups "Coypu" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coypu+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Andrew Masters

unread,
Jun 3, 2013, 7:41:38 AM6/3/13
to co...@googlegroups.com
It gets to the relevant page and then hangs around looking for the correct element (maybe stuck in some kind of loop?) - surprised it actually works at all.
It might be my specific laptop / Chrome webdriver. I'll try it at work on the same thing.

Only started using Coypu at the weekend, so everything is the latest from NuGet.

Adrian Longley

unread,
Jun 3, 2013, 1:55:28 PM6/3/13
to co...@googlegroups.com


On 3 Jun 2013, at 12:41, Andrew Masters <adma...@googlemail.com> wrote:

It gets to the relevant page and then hangs around looking for the correct element

Thanks Andy. The only thing I can thing of off the top of my head is that maybe The chrome driver is waiting around for a page load event which for some reason is delayed, but happens right away in Firefox. I would be very surprised if the wait is actually in looking for the field.

Thanks for the HTML. I'll try your code here on my setup and see if I an reproduce anything like what you see.

Adrian Longley

unread,
Jun 3, 2013, 2:19:38 PM6/3/13
to co...@googlegroups.com




On 3 Jun 2013, at 18:55, Adrian Longley <adrian...@gmail.com> wrote:



On 3 Jun 2013, at 12:41, Andrew Masters <adma...@googlemail.com> wrote:

It gets to the relevant page and then hangs around looking for the correct element

Thanks Andy. The only thing I can thing of off the top of my head is that maybe The chrome driver is waiting around for a page load event which for some reason is delayed, but happens right away in Firefox. I would be very surprised if the wait is actually in looking for the field.

Thanks for the HTML. I'll try your code here on my setup and see if I an reproduce anything like what you see.

Could you please post the exact HTML and c# code? What is below doesn't compile and wouldnt find those fields anyway with that HTML. Thanks.

Andrew Masters

unread,
Jun 5, 2013, 6:43:54 AM6/5/13
to co...@googlegroups.com
See attached files.

Test output:
Starting test with:Firefox
-00:00:01.4170810
Starting test with:Chrome
-00:01:48.1611865
contact.htm
Class1.cs
Reply all
Reply to author
Forward
0 new messages