Hi Akshaya,
Glad you were able to solve the issue. We’re slowly moving away from shm fifo
segments, i.e., /dev/shm segments, in favor of memfd segments.
Regards,
Florin
> On Nov 4, 2019, at 3:11 AM, Akshaya Nadahalli
> wrote:
>
> Hi Florin,
>
> This crash was due to setting hard limit on
Hi Florin,
This crash was due to setting hard limit on /dev/shm partition to 100 MB.
After increasing that I am able to scale more connections.
For fifo allocation, I see that we can use either shm or memfd. Is there
any recommendation/preference on which one to use? Does memfd also
internally us
Thanks Ping. Already Florin suggested to try out master code, I will try
that out and update. Somehow this mail was sent twice to mailing list by
mistake.
Regards,
Akshaya N
On Tue, Oct 29, 2019 at 12:07 PM Yu, Ping wrote:
> We have some test for VCL based on application too, and it looks fine.
We have some test for VCL based on application too, and it looks fine. To
understand more, you’d check what line in mspace_malloc trigger the signal.
Attached is our vcl.conf for you to try if it is okay.
vcl {
rx-fifo-size 5000
tx-fifo-size 5000
app-scope-local
app-scope-global
api-socket-name
