Search Results for "garbage"

...This section documents our most commonly used API methods. Additional APIs are documented in their own files within the docs folder and are accessible via the navigation list on the left side of the docs site. Garbage collection in Node is less aggressive and deterministic (due to the lack of clear idle periods that browsers have through the rendering refresh rate) which means that leaving the release of connection resources to the garbage collector can lead to excessive connection usage, reduced performance (due to less connection re-use), and even stalls or deadlocks when running out of connections.

...Don't look at the small size, its functions are still very diverse, such as multi-document drag and add start, fast key out, automatic multi-layer display, lnk file analysis, etc. The software has no complicated functions, and no garbage files will be generated during operation. Green is free of pollution. It only focuses on the rapid start of the file. It is a good helper for users to improve the operating experience of Windows.

Node Clinic is a suite of diagnostic tools for Node.js applications, designed to help developers identify and resolve performance issues, memory leaks, and other common problems in their code.

...Compiler documentation explores the Ignition interpreter, TurboFan optimizer, optimization decisions, and deoptimization behavior. Memory sections explain heap organization, garbage collection, object references, allocations, and leak investigation. Profiling material covers inspection tools, runtime flags, performance analysis, and flamegraph generation. Additional notes examine snapshots, code caching, runtime functions, and JavaScript language features from a performance perspective. The repository is primarily a technical reference for developers who want to understand why V8 and Node.js code behaves the way it does.

Duktape is easy to integrate into a C/C++ project: add duktape.c, duktape.h, and duk_config.h to your build, and use the Duktape API to call ECMAScript functions from C code and vice versa. Partial support for ECMAScript 2015 (E6) and ECMAScript 2016 (E7), Post-ES5 feature status, kangax/compat-table. Combined reference counting and mark-and-sweep garbage collection with finalization. Property virtualization using a subset of ECMAScript ES2015 Proxy object. Bytecode dump/load for caching compiled functions. Distributable includes an optional logging framework, CommonJS-based module loading implementations, CBOR bindings, etc. See duktape.org for packaged end-user downloads and documentation. ...

...Since A-Frame is built on top of the DOM, web libraries such as React, Vue.js, Angular, Ember.js, d3.js are able to sit cleanly on top of A-Frame. I recommend using vanilla A-Frame and aframe-state-component with static templating over aframe-react. React wastes a lot of cycles and incurs a lot of memory garbage. aframe-react is often abused where it is too easy to place 3D/real-time logic at the React layer, causing poor performance (e.g., doing React renders on ticks). aframe-react applications frequently ignore the prescribed ECS framework of A-Frame. Internally, React does tons of computation to compute what changed, and flushes it to the entire application. ...

Jet Slalom type game for WebOS using AJAX/Canvas/Mojo. Coded to give a range of code examples such as: using HTML5 Canvas elements; fending off the garbage collector; managing Mojo lists and widgets; global/local leaderboards; and mobile advertising.