Hello,
There's no single best optimization solution for that; If you do multiple
devices or build types at once, that's one optimization, if you do a single
target but introduce lot of changes it is another optimization, if you also
need chromium... In my setup I have/had some workers using btrfs snapshots,
some with ram drives (200+gb disk IO per build is no joke, don't want to
ruin my nvmes in a month), but in general if you need 5-6 builds a day,
then this is sure an overkill to go that deep. Queueing based on changes is
another thing (waiting to accumulate changes while not making whole
builddir dirty isn't exactly a definition of easy CI pipeline).

The best thing I could possibly recommend is renting a moderately priced
host for build server (64gb / some i7 / striped raid can be found under 50
eur/month), adding ccache, setting mitigations=off for kernel, doing a
thorough check of installclean.mk's and setting up zram + lots of swap
(bind mounts, overlayfs etc). Or if you possibly could be interested in a
more straightforward solution to save more than a day of developer's work
without spending rest of the weekend on unhealthy linux experimenting, send
me an email and we'll find a solution.



On Thu, Jun 11, 2020 at 7:55 PM Music Pie <[email protected]> wrote:

> Hello, can you tell me more about your project please
>
> On Thu, 11 Jun 2020, 8:36 pm Minghui Ma, <[email protected]> wrote:
>
>> hi all,
>>
>> What I'm looking for: On a single machine, a simple queue that accepts
>> enqueues from multiple users to be run  sequentially for make android img.
>>
>> Is there any software that does that. I've looked at task spooler.Is
>> there anything better
>>
>>
>> --
>> --
>> 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/9c18b17c-5948-486e-969f-0b5e40943639o%40googlegroups.com
>> <https://groups.google.com/d/msgid/android-building/9c18b17c-5948-486e-969f-0b5e40943639o%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/CAJX%3DaXGp37NV07bzmOp6K68uofHf_h8ardcfTCW1evRykQN9tw%40mail.gmail.com
> <https://groups.google.com/d/msgid/android-building/CAJX%3DaXGp37NV07bzmOp6K68uofHf_h8ardcfTCW1evRykQN9tw%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/CAK-rsLLP%2B%2BQ91M67KFznus%2Bh12ExFCEuPNanch9NN3E3ZKJRzA%40mail.gmail.com.

Reply via email to