On 07/21/2011 07:52 AM, Fritz Zaucker wrote: > Ok. It might be worth mentioning somewhere in the docu, as the default OS > tmp dir might be on a RAM disks that usually is not that huge.
Good point. Please open a bug for it. > Hmm, if it can be smaller, fine. On the other hand, I'd think performance is > what matters most in this context. Certainly. Disk space is so cheap. > Ok, so having a common cache would help in the first build of the second > application. Correct. > I guess this would mean if I don't fiddle with config.json, those parameters > should be the same. Correct. Bear in mind though that even introducing "environment" settings in the config changes the variant when creating the build version. >> But keep in mind that sharing is not only between different apps, but also >> between different builds of the *same* application. This is another >> important aspect of sharing. Re-building the same app would be much slower >> without the cache. > Isn't this the main (if not only) purpose of the cache? That's why I don't > want to loose it at reboot (I have almost 3 minutes for a build with clean It's certainly the more important aspect for most users. We're not (yet ;) in the era where most people work on 3-5 qooxdoo projects at the same time. - We, on the other hand, are constantly re-generating our standard apps during development (feedreader, playground, demobrowser, ...), and to us it matters *a lot*. It is probably not the only feature that was introduced with our own benefit in mind :). > cache and about 6 seconds thereafter; a really big improvement, even if most > of the development work can be done with the source version). Don't be deceived! With an empty cache generating the source version of an app is not dramatically faster than creating its build version (if you compare raw source-script/build-script performance). The main performance hog is not the compile step, where the build code is compressed, optimized and written to disk, but the code analysis for dependencies, resource needs, etc., basically: calculation of lists. And this is done in the source version just as well. T. ------------------------------------------------------------------------------ 5 Ways to Improve & Secure Unified Communications Unified Communications promises greater efficiencies for business. UC can improve internal communications as well as offer faster, more efficient ways to interact with customers and streamline customer service. Learn more! http://www.accelacomm.com/jaw/sfnl/114/51426253/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
