Thanks for your reply, and that`s very impressive. I already read the document and some examples are implemented, but there is still a long way to applied on AOSP.
We will focus on that and looking forward to your updates. 在2021年4月28日星期三 UTC+8 下午10:54:57<Ulf Adams> 写道： > Hi Eli, > > RBE stands for Remote Build Execution. It is not built into Bazel, but > there are a couple of open source as well as commercial options, documented > here: https://docs.bazel.build/versions/4.0.0/remote-execution.html > > Full disclosure: I work for one of the commercial vendors in this space > and we contributed some patches in the past to improve AOSP builds. Last I > checked, we could successfully build AOSP in ~20 minutes in the best case > scenario. > > Cheers, > > -- Ulf > > *EngFlow GmbH* > Fischerweg 51, 82194 Gröbenzell, Germany > Amtsgericht München, HRB 255664 > Geschäftsführer (Managing Director): Ulf Adams > https://www.engflow.com > > > On Wed, 24 Feb 2021 at 09:28, Eli Chang <[email protected]> wrote: > >> Hi Dan, >> >> I'm very interested in RBE, but no TAM. Could you tell me the specific >> method of building RBE on AOSP? >> >> Is RBE part of Bazel? Is there any document for reference? >> >> thanks >> >> 在2020年3月4日星期三 UTC+8 上午5:57:32<Dan Willemsen> 写道： >> >>> The build team does not recommend using Goma -- it does not work >>> particularly well with the Android build, and we expect to be removing >>> support for it in master in the coming months (support will most likely >>> still be in this years release, but not next years). >>> >>> RBE is the replacement, but it's still evolving at the moment. Many of >>> our CI builds have switched to it (they never used Goma), but only a >>> handful of developers have used it so far. If you're interested in this, >>> I'd highly recommend asking your TAM about it (or if you don't have one, >>> contact me and I can try to route your request to the right team). >>> >>> For what we're doing (other than Goma/RBE), the majority of our CI >>> builds are done on n1-standard-64 >>> <https://cloud.google.com/compute/docs/machine-types#n1_machine_type> >>> machines with SSD persistent disks. Depending on your >>> limitations/requirements, the newer C2/N2 machine families may be more >>> efficient. For local developers, we're generally buying fast desktops -- 2x >>> Intel Xeon GOLD 6154 processor (18-core Skylake, up to 3.70 GHz) with 192 >>> GB RAM and a few TB of SSDs. >>> >>> - Dan >>> >>> On Sun, Mar 1, 2020 at 11:52 PM 'Orion Hodson' via Android Building < >>> [email protected]> wrote: >>> >>>> Hi Alexander >>>> >>>> Internally Android developers use goma. The thread below has pointers >>>> to the client and server. It is built on GCP. >>>> >>>> >>>> https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/eOtBzosZtd8 >>>> >>>> Kind regards >>>> Orion >>>> >>>> On Sun, 1 Mar 2020 at 22:39, alexander zhu <[email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> I faced one problem, i have tried to solve it many days. >>>>> >>>>> >>>>> AOSP compile on one powerful physical server(36U128G) is fast . >>>>> Because my company has so many people need to compile AOSP on the >>>>> server,so >>>>> it is busy all the time , and I do not have money to buy more.But the VM >>>>> I >>>>> can request more.So I want to use VM on the cloud to compile AOSP. >>>>> >>>>> I have some distribute compile experiences in other c/c++ projects. So >>>>> I'm thinking is there any way to compile AOSP in distribute way?exp: use >>>>> many VMs for one AOSP build. >>>>> >>>>> I noticed there had topic long time ago : >>>>> https://groups.google.com/forum/#!searchin/android-building/distcc%7Csort:date/android-building/_YJNwvq6FtY/EENyTx4Elk4J >>>>> >>>>> I tried distcc , but failed . AOSP switching to clang, but distcc >>>>> support clang not ok. >>>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926884 >>>>> >>>>> >>>>> So, I want to know ,AOSP in google , how to solve the long build time >>>>> ?use more powerful physical server? or you have your own distribute >>>>> compile solution? >>>>> >>>>> -- >>>>> -- >>>>> You received this message because you are subscribed to the "Android >>>>> Building" mailing list. >>>>> To post to this group, send email to [email protected] >>>>> To unsubscribe from this group, send email to >>>>> [email protected] >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/android-building?hl=en >>>>> >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Android Building" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/android-building/e3dd71e8-e452-48e2-8686-c51e359cbf5c%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/android-building/e3dd71e8-e452-48e2-8686-c51e359cbf5c%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>>> -- >>>> You received this message because you are subscribed to the "Android >>>> Building" mailing list. >>>> To post to this group, send email to [email protected] >>>> To unsubscribe from this group, send email to >>>> [email protected] >>>> For more options, visit this group at >>>> http://groups.google.com/group/android-building?hl=en >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Android Building" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/android-building/CAAttue0u%2BuqgwNO4ggmnWsYS%2B8FmL8xURN-Xqt9sw9d1aLENQQ%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/android-building/CAAttue0u%2BuqgwNO4ggmnWsYS%2B8FmL8xURN-Xqt9sw9d1aLENQQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> -- >> You received this message because you are subscribed to the "Android >> Building" mailing list. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/android-building?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Android Building" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/android-building/fcb564b9-e266-4789-a2d7-4f2d35f20b5an%40googlegroups.com >> >> <https://groups.google.com/d/msgid/android-building/fcb564b9-e266-4789-a2d7-4f2d35f20b5an%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/e6d95971-055d-4041-b187-4b42ad6a13d8n%40googlegroups.com.
