These are chat archives for assetgraph/assetgraph

4th
Jul 2016
Munawwar
@Munawwar
Jul 04 2016 05:25
@gustavnikolaj I tried adding a cache layer to the systemjs less plugin with indexedDB. For me it does reduce load time to 1/5 th of the time compared to transpiling all less files. (i.e 250 ms -> 50 ms. Avg of 3.5 ms per file).
Peter Müller
@Munter
Jul 04 2016 06:16
Maybe we should pick up my express-systemjs-translate idea and make it actually work. That would potentially fix a lot of speed issues at once
Munawwar
@Munawwar
Jul 04 2016 06:52
nwjs/cordova here. No server. I'd rather like we invest time on fusile.
Peter Müller
@Munter
Jul 04 2016 06:56
That would certainly be nice as well. I think I know of one place where a bug might reside, but not where the file system lock comes from
Andreas Lind
@papandreou
Jul 04 2016 07:21
Could be interesting to try and get unexpected-fs to help with fuzzing incoming events and file system latencies.
Gustav Nikolaj
@gustavnikolaj
Jul 04 2016 08:02
@Munawwar I'd like to avoid the overhead of loading up the transpilers into the browser. Which requires something like @Munter's systemjs-transplate middleware :-)
but maybe there's a sweet spot that could take care of both scenarios
Andreas Lind
@papandreou
Jul 04 2016 08:04
@Munawwar The management of an in-memory and/or file system-based cache could be shared between the middleware and fusile, at least.
Munawwar
@Munawwar
Jul 04 2016 08:23
Andreas: Still seems redundant to me (or more accurately, if a memory based solution takes care of both scenarios, then the file system solution becomes obsolete). But if it makes everyone happy, then we'll have to go for it.
Munawwar
@Munawwar
Jul 04 2016 08:34
BTW, sessionStorage is way faster (since it is in-memory)...however AFAIK it is limited to 5MB of storage.
Andreas Lind
@papandreou
Jul 04 2016 08:40
@Munawwar I meant the cache that would reside inside fusile or the middleware.
Munawwar
@Munawwar
Jul 04 2016 08:41
o! ok.. yup, that could be done
Peter Müller
@Munter
Jul 04 2016 10:06
How would a shared cache work? memcache?
Also, express-systemjs-translate had the intention of not only transpiling the known cases, but also the unknown custom ones by executing systemjs plugins, exactly as you would in the browser, but just leverage the cache layer. Plus on a running basis update the systemjs config file to add dependency maps so the client could load in parallel instead of relying on incremental discovery
Munawwar
@Munawwar
Jul 04 2016 10:29
I think he was just talking about sharing the code, not memory?
^ which is very small btw
Peter Müller
@Munter
Jul 04 2016 10:30
Right. That should be doable. Incidentally that piece of code also really needs to be cleaned up in fusile. Grew organically
Peter Müller
@Munter
Jul 04 2016 11:04
http://assetgraph.com/ Ready for content :)
Andreas Lind
@papandreou
Jul 04 2016 11:15
@Munawwar @Munter Yeah, just the code to manage a cache while watching a file system dir for events.