Hi Milo's, 

Currently we are planning to make use of the following to have test initially with 8 remote switches. 

In future, we are planning further to try with more devices to run the test jobs.

Thanks for the information.

Regards, 
Dhanunjaya

On Wed, Nov 20, 2019, 18:23 Milosz Wasilewski <milosz.wasilewski@linaro.org> wrote:
On Wed, 20 Nov 2019 at 12:37, dhanu msys <dhanuskd.palnati@gmail.com> wrote:
>
> Hi Team,
>
> Now I have experienced by running some of test jobs on LAVA Setup , really lava-mailing-lists helps a lot to solve problems & providing suggestions at earliest.
>
> Now We are planning to have LAVA Lab Setup with minimum 30 to 40 devices connected to the PDU to run automation test jobs.
>
> So , at initial we wants to know the LAVA Server Specifications more in detail , like RAM etc.. to setup the LAVA Lab.

This strongly depends on your setup, builds you're going to test and
devices you're using for testing. From my experience the most resource
hungry jobs are android ones. In case of using fastboot and adb you
should allocate 1 CPU thread for 1 DUT on your worker(s). RAM isn't
that critical. Of course the more the better but it shouldn't be an
issue. You should look at IO performance. LAVA uses IO a lot. So quick
hard drives (SSDs) will be required in the setup with that many
devices. In our LAB we tend not to connect more than ~20 DUTs to
single worker. So you're probably looking at at least 2 workers.
Depending on how many jobs will run in parallel lava-logs might need
to run on a separate machine.

Which PDU are you using? The ones we have in the LAB only have 24 ports.

milosz

>
> Regards,
> Dhanunjaya. P
> _______________________________________________
> Lava-users mailing list
> Lava-users@lists.lavasoftware.org
> https://lists.lavasoftware.org/mailman/listinfo/lava-users