[tw5] Re: [tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-07 Thread @TiddlyTweeter
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

Re: [tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-07 Thread BurningTreeC
> > 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() >> > >

[tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-07 Thread PMario
On Saturday, April 7, 2018 at 11:48:55 AM UTC+2, Jed Carty wrote: > > > > I have been considering trying to use TaffyDB (http://taffydb.com > ) > > with tiddlywiki but I haven't had a chance

Re: [tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-07 Thread PMario
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() >

[tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-07 Thread Jed Carty
Looking through my things, despite using the Object.keys().forEach structure many times there is only one time I have found that may lead to any sort of performance improvement. Most of the uses are over a very small list (only one or two items generally) and only happen rarely (like when a

Re: [tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-07 Thread BurningTreeC
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

[tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-07 Thread Jed Carty
Oh, that is unfortunate. I use Object.keys.forEach a lot in my plugins because it is convenient for me to type. Also reading about how the performance of for (property in object) {..} type loops is changing is interesting. It is going to be less efficient than the object.keys().foreach option

Re: [tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-07 Thread BurningTreeC
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/ -

Re: [tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-06 Thread Jeremy Ruston
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

[tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-06 Thread 'Mark S.' via TiddlyWiki
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 the way through.

[tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-06 Thread wardjh
I will have the larger project ported over to the newest version of TW this weekend and run it off my personal server. For the smaller project I am going to keep adding 100 more records at a time in the spreadsheet until I notice that it starts to slow down. Thanks, On Friday, April 6,

[tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-06 Thread @TiddlyTweeter
BTC Good thought. I'll point the author to your suggestion. TT BurningTreeC wrote: > > For a good comparison I would like to see that big one using the latest > prerelease version, where some performance tweaks have been done > -- You received this message because you are subscribed to the

[tw] Re: The Performance At Scale Bummer ... Initial Notes

2018-04-06 Thread BurningTreeC
Hi @TiddlyTweeter For a good comparison I would like to see that big one using the latest prerelease version, where some performance tweaks have been done BTC -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and