IntervalTrigger hardcoded value
See original GitHub issueOpenUI5 version: Latest Browser/version (+device/version): Chrome latest
Hi,
I see that ui5 uses a central IntervalTrigger to dispatch events. It is created with a default/hardcoded value of 200
ms.
We would like to improve the performance for our users and thus tune this parameter (lowering the value). How can we achieve this? Is this 200
configurable?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
interval_trigger – Looker Help Center
Default Value. none. Accepts. A string containing an integer followed by a timeframe (seconds, minutes, or hours). Definition.
Read more >Pyinstaller with APScheduler - TypeError with IntervalTrigger
IntervalTrigger () as arguments, the code should be, this is where the error comes from. scheduler.add_job(Run, interval.
Read more >interval_trigger | Looker - Google Cloud
Default Value. none. Accepts. A string containing an integer followed by a timeframe (seconds, minutes, or hours) ...
Read more >tf_agents.train.interval_trigger.IntervalTrigger | TensorFlow Agents
The triggering interval. fn, callable with no arguments that gets triggered. start, An initial value for the trigger. Methods ...
Read more >sap.ui.core.IntervalTrigger - API Reference - SAPUI5 SDK
Creates an instance of EventBus. new sap.ui.core.IntervalTrigger(iInterval). Param. Type. Default Value. Description. iInterval. Type: int. Default Value:.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The
IntervalTrigger
is mainly used by theResizeHandler
, a service that regularly checks a set of registered DOM elements for size changes. It was introduced long ago because at that time there was no cross-browser resize-event available for arbitrary DOM elements, only for the window. In the recent months,ResizeObserver
became available in many modern browsers and is therefore currently being evaluated as an alternative.So the answer is NO, not all function invocations have to pass that gateway. Only a very small subset of functions is triggered by that interval. The purpose of the
ResizeHandler
is no secret, but documentation is, ehm, reduced to a minimum.Hi, I don’t have any samples right now. Is it true that (I didn’t read all the codebase) that InternalTrigger is some sort of gateway where all the function’s invocations have to pass? Or only some of them? I just would like some documentation about why this is in place and what’s its purpose.
About mobile batteries: I don’t really understand why a thread (loop) should always run every 200ms at all. In most of the cases, it will just do nothing after the page loaded.