Hi,
One of the differences between Chrome and Safari is that Chrome sets the
setTimeout clamp to 1ms as opposed to 10ms. This means that if the
application writer requests a timer of less than 10ms, Chrome will allow it,
whereas Safari will clamp the minimum timeout to 10ms. The reason we did
the performance they need while avoiding
compatibility problems.
dave
On Sep 29, 2008, at 10:06 PM, Maciej Stachowiak wrote:
On Sep 29, 2008, at 7:26 PM, Mike Belshe wrote:
Hi,
One of the differences between Chrome and Safari is that Chrome sets the
setTimeout clamp to 1ms as opposed to 10ms
Alexey Proskuryakov [EMAIL PROTECTED]
Sep 30, 2008, в 6:37 PM, Mike Belshe написал(а):
Thanks for the concrete examples, Dave! I tested all 3 of these, and
haven't yet found any problems. But I don't have specific URLs. I also
looked through the webkit bugs database as much as I could
.
As for keeping the fan off - if we could keep the CPU idle a 3ms minimum
timeout loop does that resolve your concern?
Mike
2008/9/30 Alexey Proskuryakov [EMAIL PROTECTED]
Sep 30, 2008, в 8:13 PM, Mike Belshe написал(а):
Thanks - I did see that bug. Intentionally spinning the CPU vis
setTimeout(,0
BTW - if the primary concern is not spinning the CPU, we could just drop
the throttle down to 2 or 3ms, and the CPU will be largely idle on most
machines. In a few years, with faster processors, we'll be able to drop to
1ms and still have largely idle CPU.
Would 3ms be viable in your
Subjective note:
I'm much more worried about sites spinning the CPU accidentally (e.g. they
used setTimeout(0) somewhere by accident) than I am about frame rates on
games. Using the clock as your frame rate is super buggy, and sites need to
know better. It won't work now and it won't work going
I think you've already seen this, but in case you haven't - here is the bug
where I've been tracking this. Every report I've seen related to minimum
timers is referenced in here.
http://code.google.com/p/chromium/issues/detail?id=792
I think the evidence is pretty compelling that 10ms and 1ms
If you're going to propose a new API designed for hi-res timers, it ought to
use units of microseconds instead of milliseconds.
Mike
On Tue, Sep 30, 2008 at 7:32 PM, Justin Haygood [EMAIL PROTECTED]wrote:
http://blog.justinhaygood.com/2008/09/30/proposed-high-resolution-timer-api/
It's
On Wed, Oct 1, 2008 at 4:30 PM, Peter Kasting [EMAIL PROTECTED] wrote:
On Wed, Oct 1, 2008 at 4:03 PM, Mike Belshe [EMAIL PROTECTED] wrote:
Also - Chrome currently taps into RefCountable and adds Peerable across
any RefCountable object, whether it needs Peerable or not. Strings
It took me a while to get my windows build going, so I thought I'd share
what I learned:
1) I had to completely start over with cygwin. I uninstalled and
reinstalled using the cygwin-downloader from here:
http://webkit.org/building/tools.html
2) Several components were missing from cygwin:
-
Thanks Adam.
On Tue, Oct 14, 2008 at 5:47 AM, Adam Roben [EMAIL PROTECTED] wrote:
On Oct 13, 2008, at 7:09 PM, Mike Belshe wrote:
It took me a while to get my windows build going, so I thought I'd share
what I learned:
Thanks, Mike! This kind of information is very helpful in keeping our
Hi, Haithem,
Both JSC and V8 running through the chromium tree, so you could try that.
If you run the test_shell, its pretty much just a shell for driving the
webkit engine, and it works with both JS engines.
You can find more information here for how to build it:
I'd like to understand what's going to happen with SunSpider in the future.
Here is a set of questions and criticisms. I'm interested in how these can
be addressed.
There are 3 areas I'd like to see improved in
SunSpider, some of which we've discussed before:
#1: SunSpider is currently version
On Sat, Jul 4, 2009 at 3:27 PM, Maciej Stachowiak m...@apple.com wrote:
On Jul 4, 2009, at 11:47 AM, Mike Belshe wrote:
I'd like to understand what's going to happen with SunSpider in the future.
Here is a set of questions and criticisms. I'm interested in how these can
be addressed
On Mon, Jul 6, 2009 at 10:11 AM, Geoffrey Garen gga...@apple.com wrote:
So, what you end up with is after a couple of years, the slowest test in
the suite is the most significant part of the score. Further, I'll predict
that the slowest test will most likely be the least relevant test,
As I said, we can argue the mix of tests forever, but it is not useful.
Yes, I would test using top-100 sites. In the future, if a benchmark
claims to have a representative mix, it should document why. Right?
Are you saying that you did see Regex as being such a high percentage of
javascript
On Sat, Jul 4, 2009 at 3:27 PM, Maciej Stachowiak m...@apple.com wrote:
On Jul 4, 2009, at 11:47 AM, Mike Belshe wrote:
I'd like to understand what's going to happen with SunSpider in the future.
Here is a set of questions and criticisms. I'm interested in how these can
be addressed
On Tue, Jul 7, 2009 at 4:20 PM, Maciej Stachowiak m...@apple.com wrote:
On Jul 7, 2009, at 4:01 PM, Mike Belshe wrote:
I'd like benchmarks to:
a) have meaning even as browsers change over time
b) evolve. as new areas of JS (or whatever) become important, the
benchmark should have
On Tue, Jul 7, 2009 at 7:01 PM, Maciej Stachowiak m...@apple.com wrote:
On Jul 7, 2009, at 6:43 PM, Mike Belshe wrote:
(There are other benchmarks that use summation, for example iBench, though
I am not sure these are examples of excellent benchmarks. Any benchmark that
consists
Overall, I think the general idea.
I'm concerned about the head-of-line blocking that it introduces. If an
administrator poorly constructs the bundle, he could significantly hurt
perf. Instead of using gzip, you could use a framer which chunked items
before gzipping. This might be more trouble
On Wed, Nov 18, 2009 at 2:47 PM, Mike Belshe m...@belshe.com wrote:
Overall, I think the general idea.
I meant to say Overall I like the general idea
I'm concerned about the head-of-line blocking that it introduces. If an
administrator poorly constructs the bundle, he could
subtle stuff - web designers could think they are speeding
up their pages when they're slowing them down. The tools need to prevent
that. It can't be manual.
Mike
-Steve
Mike Belshe wrote:
Alexander - when you do the testing on this, one case I'd really like to
see results
reducing the time between
tests (as sugested by Mike Belshe) to avoid the negative impact of power
management on many systems (both Mac and Windows), and which are most
apparent for very fast browsers.
I'm deliberately not posting this on the web site yet because I don't want
a flood
On Tue, Dec 15, 2009 at 1:01 PM, Maciej Stachowiak m...@apple.com wrote:
On Dec 15, 2009, at 12:30 PM, Mike Belshe wrote:
[+cc John Resig since he's using this as part of dromaeo]
Overall, sounds like good progress.
A couple of ideas:
- can we make it so that if you try to cut
Hi -
I've been working on SPDY, but I think I may have found a good performance
win for HTTP. Specifically, if the PreloadScanner, which is responsible for
scanning ahead within an HTML document to find subresources, is throttled
today. The throttling is intentional and probably sometimes
On Thu, Jan 7, 2010 at 12:49 PM, Maciej Stachowiak m...@apple.com wrote:
On Jan 7, 2010, at 12:09 PM, Mike Belshe wrote:
Hi -
I've been working on SPDY, but I think I may have found a good performance
win for HTTP. Specifically, if the PreloadScanner, which is responsible for
scanning
it on selectively for ports that want it.
Mike
Maybe there’s a good middle-ground, where PreloadScanner is run more often
but still does the priority sorting?
Joe
*From:* webkit-dev-boun...@lists.webkit.org [mailto:
webkit-dev-boun...@lists.webkit.org] *On Behalf Of *Mike Belshe
*Sent
Hi,
I tend to hit code which is often chromium-platform specific. It's hard to
know the appropriate Platform and OS fields for such a bug. For
instance, I am working on a small change to WebKit/chromium/src/WebKit.cpp.
It's not a Mac bug, its not a PC bug, its a Chromium bug.
Chromium is a
2011/1/14 Maciej Stachowiak m...@apple.com
On Jan 13, 2011, at 2:49 PM, Gavin Peters (蓋文彼德斯) wrote:
Thanks everyone for your replies on link headers and rel types.
Mike Belshe from Chrome team put together a spec for these as part of
Server Hints for SPDY. His server hint information
29 matches
Mail list logo
