On Thu, Jan 14, 2010 at 10:34 AM, Alexey Proskuryakov <a...@webkit.org> wrote:
> > On 13.01.2010, at 17:00, Darin Adler wrote: > > 6.87 secs: websocket/tests/frame-lengths.html >> > > This test verifies that packet size computation logic is correct for all > message sizes from 0 to 1025. We've had bugs in this area before, and it's > hard to ensure adequate coverage without testing all message sizes. > > I haven't checked if the bottleneck is server-side or client-side, and > actually assumed that this is a reasonable time to make 1K connections. Sorry, I don't remember what bugs in this area. Can we do test only boundary case? > > 3.63 secs: websocket/tests/simple-stress.html >> > > This test sends a thousand of short messages simultaneously, and one huge > one (256K). I think that it is an important stress test to keep. > > > 1.18 secs: websocket/tests/bad-sub-protocol.html >> > > This test can be made faster by executing subtests in parallel. > I'll do it: https://bugs.webkit.org/show_bug.cgi?id=33646 -- ukai > > - WBR, Alexey Proskuryakov > > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
