W3C home > Mailing lists > Public > public-device-apis-log@w3.org > December 2016

Re: [sensors] Don't allocate response objects to avoid triggering GC

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Fri, 09 Dec 2016 13:22:53 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-266012570-1481289771-sysbot+gh@w3.org>
Garbage collection pauses causing missed frames are well known and 
well documented issues. Note the issue isn't the extra allocation 
time, it's the GC pauses.

Among the TAG requests (coming from @slightlyoff) was a requirement to
 make this available off of the main thread for fear of jank.

Designing CPU-hungry APIs designed for perf-sensitive applications 
with performance in mind isn't premature optimization, it's just Doing
 the Right Thing[TM]. ;)

That said, I'd love to see test data if there's some easily available,
 but I don't think the onus is on the OP to prove his point here, 
rather it's on us to explain how the current design is going to avoid 
causing GC pauses when GC kicks in.

-- 
GitHub Notification of comment by tobie
Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/153#issuecomment-266012570 using
 your GitHub account
Received on Friday, 9 December 2016 13:23:01 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:52 UTC