Hi, >I already set the cache to a folder in a ram disk. >It improve speed but I would like more. > >So, I did try to put the entire SDK in a ram disk. >This is the best IO bandwidth I could think about.
This doesn't surprise me at all. Ramdisks make situations faster where you _write_ to disk; not when reading, because unix-based server usually use about half of their memory as file-system-cache. Most of performance is related to python not being a very fast language. However, the way python is used here, sounds like a good case for the 'psyco': Take a look at; http://psyco.sourceforge.net/ As to your specific case. I would just use a pre-bundled qooxdoo library, like Petr suggested. That would make it madly quick and doesn't require a lot of effort on your part. *Long term qooxdoo-development-wise. * * * Perhaps it would make more sense to write the generator in a language more suitable for that particular goal, like Haskell? If I would a proper understanding of everything it does, I would give it a go myself. The sort of computation it seems to do is very stream based. I wouldn't recommend Haskell for a lot of tasks, but for a tool like that, it should be the first considered candidate. It would have very good performance, require very little code to write, and we can easily assert it to be semantically correct. One of the nice advantages of having a parser in Haskell, is that it would be very easy to add some javascript optimizations for the less intelligent browsers out there. Stuff like converting: myObject.someMethod( foo[bar], foo[bar] ); To: var foobar = foo[bar]; myObject.someMethod( foobar, foobar ); As for ready to go javascript parsers & pretty printers for Haskell, see: http://hackage.haskell.org/package/WebBits -- Greetings, -- Ralf 2010/8/16 Jean-Baptiste BRIAUD -- Novlog <[email protected]> > Hi, > > I was wondering how I could speed up the generate script. > > I just remind that because we are generating all the source code for an > application (qx client, Java server, SQL), that script is launched quite > often. > That step (generate build) currently take about 90% of the total time to > create an application (generate files, compile backend, create qooxdoo > application, install database schema, deploying...). > > I already set the cache to a folder in a ram disk. > It improve speed but I would like more. > > So, I did try to put the entire SDK in a ram disk. > This is the best IO bandwidth I could think about. > > To my surprise the time for a generate build didn't improve. > Tests had been done with an empty cache so the difference would be only due > to the SDK in a ram disk. > No difference (less than 5%) while the bandwidth of the ram disk is far > more than 5% compare to the HDD. > > So, what else could I try to improve that speed, any advices, ideas ? > > Thanks ! > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
