I usually have about 10 projects and 1000 files. Maybe this question would be better on buildr-users instead of -dev, to involve more of the community.
Lacton On Wed, Nov 5, 2008 at 11:57 PM, Assaf Arkin <[EMAIL PROTECTED]> wrote: > On Wed, Nov 5, 2008 at 1:10 AM, Ittay Dror <[EMAIL PROTECTED]> wrote: >> >> The reason I'm requesting this is that I have a buildfile with 150 projects >> and the current way Buildr works, by invoking all projects takes too much >> time when I want to build just a single project (and its dependencies of >> course). On developer windows machine this "warmup" time is ~15 seconds and >> is increasing as more modules are added. From my tests, this patch can lower >> it to just a few seconds. > > The reason I asked you to bring this back to the mailing list is the size > issue. > > The projects I'm working on have, in the order of 1000~5000 files (not > just source code), 5~25 projects, warmup around a second. > Occasionally I would test things out against a larger corpus of code, > ~50,000 files, I'm happy when that turns to go under 5 seconds. Only > because I consider that at the top scale of what a single buildfile is > expected to support. > > There are certain optimizations you can make that would benefits the > smaller sizes (the 1000~5000 above), and would be acceptable on larger > size (~50,000), but might be a drag on larger buildfiles. I never > test with anything larger because I think the soft spot, the majority > of uses fall in the smaller scale. Anything substantially larger you > would want to (well, at least me) break up. > > So I'm wondering where do other people stand on this? What's the size > range you expect buildfiles to be optimized for? > > Assaf > > >> >> Ittay >> >> -- >> -- >> Ittay Dror <[EMAIL PROTECTED]> >> >
