tzssangglass commented on issue #5837:
URL: https://github.com/apache/apisix/issues/5837#issuecomment-1174519045
> Can you tell me which plugin I can modify to get information of
`ngx.shared.DICT` regularly and report it? prometheus?
yes, prometheus.
--
This is an automated
tzssangglass commented on issue #5837:
URL: https://github.com/apache/apisix/issues/5837#issuecomment-1173658046
Hi @ccxhwmy , would you like to work on this?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
tzssangglass commented on issue #5837:
URL: https://github.com/apache/apisix/issues/5837#issuecomment-1173262871
> I found that nginx adopts a way of pre-allocating memory for shared DICT,
the smallest granularity is page, ranther than allocat per use. The value of
tzssangglass commented on issue #5837:
URL: https://github.com/apache/apisix/issues/5837#issuecomment-1080100342
we can use `ngx.shared.DICT.capacity` and `ngx.shared.DICT.free_space` to
monitor a `ngx.shared.DICT`?
--
This is an automated message from the Apache Git Service.
To respond
tzssangglass commented on issue #5837:
URL: https://github.com/apache/apisix/issues/5837#issuecomment-1079713346
I changed my mind and I think it's a meaningful enhancemen.
Perhaps we can first monitor the nginx.shared.DICT that is used by APISIX,
and next we allow users to monitor
tzssangglass commented on issue #5837:
URL: https://github.com/apache/apisix/issues/5837#issuecomment-997520329
It seems to be quite difficult, and if you use the ngx.shared.DICT API to
monitor it, it will lose performance.
refer to:
