Re: GWT Distrubted Compiler Project
OK let me know. Currently the system basically works (you can run a distributed build) but it could probably use some help in terms of just trying it out and finding the kinks. Cheers, Dobes On Tue, Jul 27, 2010 at 3:30 PM, Gal Dolber wrote: > Love your idea... even compiling a medium project in a macbook right now is > a pain in the ass. > I am out of time right now but I will love to help in a near future > > 2010/7/27 Dobes >> >> The google code project for this is at >> http://code.google.com/p/gwt-distcc/ >> >> On Jul 27, 3:05 pm, Dobes wrote: >> > Hi, >> > >> > I've been working on a distributed compiler project, to speed up >> > compile times by distributing the work across many machines. Useful >> > for those times when the compiler takes a long time and you have a lot >> > of permutations. >> > >> > Since its a bit of a side-project I'm hoping some other will jump on >> > board and help out. >> > >> > This project provides an AppEngine? based server and java clients that >> > distribute GWT permutation compiles automatically over participating >> > computers. >> > >> > Symmetric keys are used to protect the privacy of your data. >> > >> > How it works: >> > >> > 1. The team agrees on the queue ID and symmetric key for their builds >> > 2. They select or deploy the server >> > 3. They run any number of build slaves and configure them to watch >> > that queue on that server >> > 4. When building, they use the DistCompile? class to compile instead >> > of the Compile class >> > 5. DistCompile? does a pre-compile (non-permutation specific), then >> > uploads the results to the central server on AppEngine? >> > 6. Build Slaves who are polling the server download the precompiled >> > file and perform a permutation compile, then upload the results to the >> > server again >> > 7. The compile client downloads build results until it has all the >> > permutations >> > 8 . Then it runs Link with the results and your build is done, >> > hopefully faster than if you did it all locally >> > >> > The best use case for this is if you have a few extra PCs and want to >> > do your work on a laptop or something without a lot of memory/CPU. >> > For example, one of my co-workers is taking >40 minutes to build our >> > GWT stuff; I'm hoping this can bring it down to 5-10 minutes instead. >> > >> > Please contact me if you're willing to help with: >> > >> > 1. Suggestions (file them in the issue tracker) >> > 2. Patches (put them in the issue tracker, too) >> > 3. Active Development (be happy to give you contributor access) >> > 4. Testing (file the bugs ...) >> > >> > Thanks in advance! >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> To post to this group, send email to google-web-tool...@googlegroups.com. >> To unsubscribe from this group, send email to >> google-web-toolkit+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> > > > > -- > http://ajax-development.blogspot.com/ > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Distrubted Compiler Project
Thanks, Jim! I had found those before. On Tue, Jul 27, 2010 at 3:35 PM, Jim Douglas wrote: > You might be interested in these references, Dobes: > > http://code.google.com/p/google-web-toolkit/wiki/DistributedBuilds > http://development.lombardi.com/?p=993 > http://development.lombardi.com/?p=1027 > > On Jul 27, 3:17 pm, Dobes wrote: >> The google code project for this is athttp://code.google.com/p/gwt-distcc/ >> >> On Jul 27, 3:05 pm, Dobes wrote: >> >> >> >> > Hi, >> >> > I've been working on a distributed compiler project, to speed up >> > compile times by distributing the work across many machines. Useful >> > for those times when the compiler takes a long time and you have a lot >> > of permutations. >> >> > Since its a bit of a side-project I'm hoping some other will jump on >> > board and help out. >> >> > This project provides an AppEngine? based server and java clients that >> > distribute GWT permutation compiles automatically over participating >> > computers. >> >> > Symmetric keys are used to protect the privacy of your data. >> >> > How it works: >> >> > 1. The team agrees on the queue ID and symmetric key for their builds >> > 2. They select or deploy the server >> > 3. They run any number of build slaves and configure them to watch >> > that queue on that server >> > 4. When building, they use the DistCompile? class to compile instead >> > of the Compile class >> > 5. DistCompile? does a pre-compile (non-permutation specific), then >> > uploads the results to the central server on AppEngine? >> > 6. Build Slaves who are polling the server download the precompiled >> > file and perform a permutation compile, then upload the results to the >> > server again >> > 7. The compile client downloads build results until it has all the >> > permutations >> > 8 . Then it runs Link with the results and your build is done, >> > hopefully faster than if you did it all locally >> >> > The best use case for this is if you have a few extra PCs and want to >> > do your work on a laptop or something without a lot of memory/CPU. >> > For example, one of my co-workers is taking >40 minutes to build our >> > GWT stuff; I'm hoping this can bring it down to 5-10 minutes instead. >> >> > Please contact me if you're willing to help with: >> >> > 1. Suggestions (file them in the issue tracker) >> > 2. Patches (put them in the issue tracker, too) >> > 3. Active Development (be happy to give you contributor access) >> > 4. Testing (file the bugs ...) >> >> > Thanks in advance! > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Distrubted Compiler Project
Hi Charlie, If you use an RSS reader you can monitor different aspects of the project using the project "feeds": http://code.google.com/p/gwt-distcc/feeds For example, you could monitor downloads if you wanted to know any time a new build was posted. If you prefer email you can use an RSS to email service, there are several free ones out there. Cheers, Dobes On Tue, Jul 27, 2010 at 3:36 PM, charlie wrote: > Is there a way to 'follow' this project on google code ? > > On Tue, Jul 27, 2010 at 5:30 PM, Gal Dolber wrote: >> >> Love your idea... even compiling a medium project in a macbook right now >> is a pain in the ass. >> I am out of time right now but I will love to help in a near future >> >> 2010/7/27 Dobes >>> >>> The google code project for this is at >>> http://code.google.com/p/gwt-distcc/ >>> >>> On Jul 27, 3:05 pm, Dobes wrote: >>> > Hi, >>> > >>> > I've been working on a distributed compiler project, to speed up >>> > compile times by distributing the work across many machines. Useful >>> > for those times when the compiler takes a long time and you have a lot >>> > of permutations. >>> > >>> > Since its a bit of a side-project I'm hoping some other will jump on >>> > board and help out. >>> > >>> > This project provides an AppEngine? based server and java clients that >>> > distribute GWT permutation compiles automatically over participating >>> > computers. >>> > >>> > Symmetric keys are used to protect the privacy of your data. >>> > >>> > How it works: >>> > >>> > 1. The team agrees on the queue ID and symmetric key for their builds >>> > 2. They select or deploy the server >>> > 3. They run any number of build slaves and configure them to watch >>> > that queue on that server >>> > 4. When building, they use the DistCompile? class to compile instead >>> > of the Compile class >>> > 5. DistCompile? does a pre-compile (non-permutation specific), then >>> > uploads the results to the central server on AppEngine? >>> > 6. Build Slaves who are polling the server download the precompiled >>> > file and perform a permutation compile, then upload the results to the >>> > server again >>> > 7. The compile client downloads build results until it has all the >>> > permutations >>> > 8 . Then it runs Link with the results and your build is done, >>> > hopefully faster than if you did it all locally >>> > >>> > The best use case for this is if you have a few extra PCs and want to >>> > do your work on a laptop or something without a lot of memory/CPU. >>> > For example, one of my co-workers is taking >40 minutes to build our >>> > GWT stuff; I'm hoping this can bring it down to 5-10 minutes instead. >>> > >>> > Please contact me if you're willing to help with: >>> > >>> > 1. Suggestions (file them in the issue tracker) >>> > 2. Patches (put them in the issue tracker, too) >>> > 3. Active Development (be happy to give you contributor access) >>> > 4. Testing (file the bugs ...) >>> > >>> > Thanks in advance! >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Google Web Toolkit" group. >>> To post to this group, send email to google-web-tool...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> google-web-toolkit+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/google-web-toolkit?hl=en. >>> >> >> >> >> -- >> http://ajax-development.blogspot.com/ >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> To post to this group, send email to google-web-tool...@googlegroups.com. >> To unsubscribe from this group, send email to >> google-web-toolkit+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. > > > > -- > > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Distrubted Compiler Project
Is there a way to 'follow' this project on google code ? On Tue, Jul 27, 2010 at 5:30 PM, Gal Dolber wrote: > Love your idea... even compiling a medium project in a macbook right now is > a pain in the ass. > I am out of time right now but I will love to help in a near future > > 2010/7/27 Dobes > > The google code project for this is at >> http://code.google.com/p/gwt-distcc/ >> >> On Jul 27, 3:05 pm, Dobes wrote: >> > Hi, >> > >> > I've been working on a distributed compiler project, to speed up >> > compile times by distributing the work across many machines. Useful >> > for those times when the compiler takes a long time and you have a lot >> > of permutations. >> > >> > Since its a bit of a side-project I'm hoping some other will jump on >> > board and help out. >> > >> > This project provides an AppEngine? based server and java clients that >> > distribute GWT permutation compiles automatically over participating >> > computers. >> > >> > Symmetric keys are used to protect the privacy of your data. >> > >> > How it works: >> > >> > 1. The team agrees on the queue ID and symmetric key for their builds >> > 2. They select or deploy the server >> > 3. They run any number of build slaves and configure them to watch >> > that queue on that server >> > 4. When building, they use the DistCompile? class to compile instead >> > of the Compile class >> > 5. DistCompile? does a pre-compile (non-permutation specific), then >> > uploads the results to the central server on AppEngine? >> > 6. Build Slaves who are polling the server download the precompiled >> > file and perform a permutation compile, then upload the results to the >> > server again >> > 7. The compile client downloads build results until it has all the >> > permutations >> > 8 . Then it runs Link with the results and your build is done, >> > hopefully faster than if you did it all locally >> > >> > The best use case for this is if you have a few extra PCs and want to >> > do your work on a laptop or something without a lot of memory/CPU. >> > For example, one of my co-workers is taking >40 minutes to build our >> > GWT stuff; I'm hoping this can bring it down to 5-10 minutes instead. >> > >> > Please contact me if you're willing to help with: >> > >> > 1. Suggestions (file them in the issue tracker) >> > 2. Patches (put them in the issue tracker, too) >> > 3. Active Development (be happy to give you contributor access) >> > 4. Testing (file the bugs ...) >> > >> > Thanks in advance! >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> To post to this group, send email to google-web-tool...@googlegroups.com. >> To unsubscribe from this group, send email to >> google-web-toolkit+unsubscr...@googlegroups.com >> . >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> >> > > > -- > http://ajax-development.blogspot.com/ > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Distrubted Compiler Project
You might be interested in these references, Dobes: http://code.google.com/p/google-web-toolkit/wiki/DistributedBuilds http://development.lombardi.com/?p=993 http://development.lombardi.com/?p=1027 On Jul 27, 3:17 pm, Dobes wrote: > The google code project for this is athttp://code.google.com/p/gwt-distcc/ > > On Jul 27, 3:05 pm, Dobes wrote: > > > > > Hi, > > > I've been working on a distributed compiler project, to speed up > > compile times by distributing the work across many machines. Useful > > for those times when the compiler takes a long time and you have a lot > > of permutations. > > > Since its a bit of a side-project I'm hoping some other will jump on > > board and help out. > > > This project provides an AppEngine? based server and java clients that > > distribute GWT permutation compiles automatically over participating > > computers. > > > Symmetric keys are used to protect the privacy of your data. > > > How it works: > > > 1. The team agrees on the queue ID and symmetric key for their builds > > 2. They select or deploy the server > > 3. They run any number of build slaves and configure them to watch > > that queue on that server > > 4. When building, they use the DistCompile? class to compile instead > > of the Compile class > > 5. DistCompile? does a pre-compile (non-permutation specific), then > > uploads the results to the central server on AppEngine? > > 6. Build Slaves who are polling the server download the precompiled > > file and perform a permutation compile, then upload the results to the > > server again > > 7. The compile client downloads build results until it has all the > > permutations > > 8 . Then it runs Link with the results and your build is done, > > hopefully faster than if you did it all locally > > > The best use case for this is if you have a few extra PCs and want to > > do your work on a laptop or something without a lot of memory/CPU. > > For example, one of my co-workers is taking >40 minutes to build our > > GWT stuff; I'm hoping this can bring it down to 5-10 minutes instead. > > > Please contact me if you're willing to help with: > > > 1. Suggestions (file them in the issue tracker) > > 2. Patches (put them in the issue tracker, too) > > 3. Active Development (be happy to give you contributor access) > > 4. Testing (file the bugs ...) > > > Thanks in advance! -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Distrubted Compiler Project
Love your idea... even compiling a medium project in a macbook right now is a pain in the ass. I am out of time right now but I will love to help in a near future 2010/7/27 Dobes > The google code project for this is at > http://code.google.com/p/gwt-distcc/ > > On Jul 27, 3:05 pm, Dobes wrote: > > Hi, > > > > I've been working on a distributed compiler project, to speed up > > compile times by distributing the work across many machines. Useful > > for those times when the compiler takes a long time and you have a lot > > of permutations. > > > > Since its a bit of a side-project I'm hoping some other will jump on > > board and help out. > > > > This project provides an AppEngine? based server and java clients that > > distribute GWT permutation compiles automatically over participating > > computers. > > > > Symmetric keys are used to protect the privacy of your data. > > > > How it works: > > > > 1. The team agrees on the queue ID and symmetric key for their builds > > 2. They select or deploy the server > > 3. They run any number of build slaves and configure them to watch > > that queue on that server > > 4. When building, they use the DistCompile? class to compile instead > > of the Compile class > > 5. DistCompile? does a pre-compile (non-permutation specific), then > > uploads the results to the central server on AppEngine? > > 6. Build Slaves who are polling the server download the precompiled > > file and perform a permutation compile, then upload the results to the > > server again > > 7. The compile client downloads build results until it has all the > > permutations > > 8 . Then it runs Link with the results and your build is done, > > hopefully faster than if you did it all locally > > > > The best use case for this is if you have a few extra PCs and want to > > do your work on a laptop or something without a lot of memory/CPU. > > For example, one of my co-workers is taking >40 minutes to build our > > GWT stuff; I'm hoping this can bring it down to 5-10 minutes instead. > > > > Please contact me if you're willing to help with: > > > > 1. Suggestions (file them in the issue tracker) > > 2. Patches (put them in the issue tracker, too) > > 3. Active Development (be happy to give you contributor access) > > 4. Testing (file the bugs ...) > > > > Thanks in advance! > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- http://ajax-development.blogspot.com/ -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Distrubted Compiler Project
The google code project for this is at http://code.google.com/p/gwt-distcc/ On Jul 27, 3:05 pm, Dobes wrote: > Hi, > > I've been working on a distributed compiler project, to speed up > compile times by distributing the work across many machines. Useful > for those times when the compiler takes a long time and you have a lot > of permutations. > > Since its a bit of a side-project I'm hoping some other will jump on > board and help out. > > This project provides an AppEngine? based server and java clients that > distribute GWT permutation compiles automatically over participating > computers. > > Symmetric keys are used to protect the privacy of your data. > > How it works: > > 1. The team agrees on the queue ID and symmetric key for their builds > 2. They select or deploy the server > 3. They run any number of build slaves and configure them to watch > that queue on that server > 4. When building, they use the DistCompile? class to compile instead > of the Compile class > 5. DistCompile? does a pre-compile (non-permutation specific), then > uploads the results to the central server on AppEngine? > 6. Build Slaves who are polling the server download the precompiled > file and perform a permutation compile, then upload the results to the > server again > 7. The compile client downloads build results until it has all the > permutations > 8 . Then it runs Link with the results and your build is done, > hopefully faster than if you did it all locally > > The best use case for this is if you have a few extra PCs and want to > do your work on a laptop or something without a lot of memory/CPU. > For example, one of my co-workers is taking >40 minutes to build our > GWT stuff; I'm hoping this can bring it down to 5-10 minutes instead. > > Please contact me if you're willing to help with: > > 1. Suggestions (file them in the issue tracker) > 2. Patches (put them in the issue tracker, too) > 3. Active Development (be happy to give you contributor access) > 4. Testing (file the bugs ...) > > Thanks in advance! -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
GWT Distrubted Compiler Project
Hi, I've been working on a distributed compiler project, to speed up compile times by distributing the work across many machines. Useful for those times when the compiler takes a long time and you have a lot of permutations. Since its a bit of a side-project I'm hoping some other will jump on board and help out. This project provides an AppEngine? based server and java clients that distribute GWT permutation compiles automatically over participating computers. Symmetric keys are used to protect the privacy of your data. How it works: 1. The team agrees on the queue ID and symmetric key for their builds 2. They select or deploy the server 3. They run any number of build slaves and configure them to watch that queue on that server 4. When building, they use the DistCompile? class to compile instead of the Compile class 5. DistCompile? does a pre-compile (non-permutation specific), then uploads the results to the central server on AppEngine? 6. Build Slaves who are polling the server download the precompiled file and perform a permutation compile, then upload the results to the server again 7. The compile client downloads build results until it has all the permutations 8 . Then it runs Link with the results and your build is done, hopefully faster than if you did it all locally The best use case for this is if you have a few extra PCs and want to do your work on a laptop or something without a lot of memory/CPU. For example, one of my co-workers is taking >40 minutes to build our GWT stuff; I'm hoping this can bring it down to 5-10 minutes instead. Please contact me if you're willing to help with: 1. Suggestions (file them in the issue tracker) 2. Patches (put them in the issue tracker, too) 3. Active Development (be happy to give you contributor access) 4. Testing (file the bugs ...) Thanks in advance! -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
