The discussion in this thread is interesting to me.
At a practical level its, perhaps, worth noting that in the last year I put
three projects "on hold" because TW testing indicated it could not cope.
FWIW, they are ...
1 - 50,000 simple sections from the Perry Mason TV series scripts. The idea
>
> On Saturday, April 7, 2018 at 9:21:49 AM UTC+2, BurningTreeC wrote:
>>
>> From the second link, requestIdleCallback() appears to be very
>> interesting - if the browser support is given. It reschedules workloads to
>> idle-time like requestAnimationFrame()
>>
>
> https://caniuse.com/#search=
On Saturday, April 7, 2018 at 9:21:49 AM UTC+2, BurningTreeC wrote:
>
> From the second link, requestIdleCallback() appears to be very interesting
> - if the browser support is given. It reschedules workloads to idle-time
> like requestAnimationFrame()
>
https://caniuse.com/#search=requestIdleCa
In the first link I posted it shows something notable about using "delete"
for deleting object properties:
In V8 6.0 and 6.1 (not yet used in any Node releases), deleting the last
property added to an object hits a fast path in V8, and thus it is faster,
even, than setting to undefined. This i
I found two interesting pages that are quite up-to-date and talk about
javascript performance on nodejs (v8) and the second on firefox:
-
https://www.nearform.com/blog/node-js-is-getting-a-new-v8-with-turbofan/
-
https://developer.mozilla.org/en-US/Firefox/Performance_best_practic
Hi Mark
> My first attempt to import the tiddlers into a pre-release version crashed
> the browser tab. So I thought that maybe I needed to use node to render out
> the tiddlers as tids. Now we hit another scalability wall. The process has
> been running 30 minutes and isn't even a quarter of t
6 matches
Mail list logo
