From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] JS1
Date: Sat, 12 Aug 2017 03:30:52 -0400 [thread overview]
Message-ID: <20170712033052.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1708112337080.25964@carhart.net>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
Interesting that you should point this out.
My throttle is only valid for intervals, which fire repeatedly.
There are no restrictions on timers, which fire only once.
So if a timer is scheduled for now + 10ms, then it fires at now + 10ms.
However, if that timer schedules another timer for now + 10 ms, then that timer fires in 10 ms, and it continues every 10 ms, and you have found a way around my restriction.
In any browser, that's more resource intensive than a 10 ms interval.
We're constantly creating objects every 10 ms, which gc must clean up before they accumulate, etc.
It's so inefficient I'm guessing nobody would do this, except maybe an acid test.
Karl Dahlke
next prev parent reply other threads:[~2017-08-12 7:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 2:49 Karl Dahlke
2017-07-24 17:57 ` Adam Thompson
2017-07-28 17:39 ` Karl Dahlke
2017-07-28 19:51 ` Adam Thompson
2017-07-28 22:05 ` Karl Dahlke
2017-08-11 7:46 ` Adam Thompson
2017-08-11 9:51 ` Karl Dahlke
2017-08-12 7:20 ` Kevin Carhart
2017-08-12 7:30 ` Karl Dahlke [this message]
2017-08-12 8:06 ` Kevin Carhart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170712033052.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).