200 forks will likely not be achievable. Although we attempt to spawn that many forks based on your setting, you will create too much CPU contention on the single core that manages all of the forks, that you are likely to never see that many.
Somewhere between 50-75 is often the max that most people will ever see. On Mon, Oct 18, 2021 at 3:32 AM nds.ap...@gmail.com <nds.apram...@gmail.com> wrote: > Hi, > > We have about 500 hosts and we were testing the ssh connections that run > in parallel at a given point before running the actual playbooks as we were > hitting bottlenecks. > > Ansible version being used: 2.10.5 > > Its a simple playbook which runs "ls" command on all the hosts. > > QUERY 1: > ----------- > > Set the forks to 200 but i see the increment happening at max 64 ssh > sessions/second using a watch command: (RAM 64 gb, 8 cores) > > I was under the impression that Forks when set would indicate that many > hosts the ssh connections would be created in parallel but thats not the > case. > > I should be seeing 200 ssh connection at once. > > Can you please let me know if i am missing anything here? (pipelining, > controlpath everything is set) > > > QUERY 2: > ------------- > Also tried with the mitogen and non mitogen strategy and see the following: > > *strategy: free* > Monday 18 October 2021 00:25:15 -0700 (0:00:05.505) *0:00:17.968* > ******** > =============================================================================== > > Run traffic from sources > ----------------------------------------------------------------------------------------------------------*-- > 5.51s* > > Here it says plabook took 5.51 seconds but if you see the time above its > 17 minutes > > *with Mitogen* > > Monday 18 October 2021 00:26:29 -0700 (0:00:12.428) *0:00:12.529* > ******** > =============================================================================== > > Run traffic from sources > ----------------------------------------------------------------------------------------------------------- > *12.43s* > Here the time almost matches. > > Why this discrepancies seen for strategy set time does not match? Any > reason? > what time should be considered here? > > Regards > Aprameya > > > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ansible-project+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/26ca4254-f5fe-4a4a-884a-4a2c47aa4c1cn%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/26ca4254-f5fe-4a4a-884a-4a2c47aa4c1cn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Matt Martz @sivel sivel.net -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAD8N0v8DntzWvycDtdOpOyObEdqB3K4ewMA%3D2p0GG6OiZhw_Zg%40mail.gmail.com.
