Date: Mon, 12 Dec 2016 14:34:34 +0100 From: Ed Schouten <ed@nuxi.nl> To: Jonathan Anderson <jonathan@freebsd.org> Cc: Allan Jude <allanjude@freebsd.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Sysctl as a Service, or: making sysctl(3) more friendly for monitoring systems Message-ID: <CABh_MKkAoTj4wA9oTz-fK0rokgMfuiUWpLt6t=qRXy6vvCh7rg@mail.gmail.com> In-Reply-To: <200A5D70-24CE-4843-B99D-E10A2AF4F68F@FreeBSD.org> References: <CABh_MKk87hJTsu1ETX8Ffq9E8gqRPELeSEKzf1jKk_wwUROgAw@mail.gmail.com> <eea0aa41-2bbc-0ddc-d951-f495c5ba2341@freebsd.org> <200A5D70-24CE-4843-B99D-E10A2AF4F68F@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Jonathan,
2016-12-11 21:12 GMT+01:00 Jonathan Anderson <jonathan@freebsd.org>:
> Rather than doing lots of system calls to
> enumerate clearly-related sysctl values, it would be very cool to do one
> system call and then inspect the resulting data structure in memory.
I'm not sure it's worth tackling this problem at this time. My current
version of the exporter is already pretty fast:
$ time ./prometheus_sysctl_exporter | wc -l
0.00 real 0.00 user 0.00 sys
3162
If our sysctl tree would get substantially larger at some point, we
should of course revisit this.
--
Ed Schouten <ed@nuxi.nl>
Nuxi, 's-Hertogenbosch, the Netherlands
KvK-nr.: 62051717
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABh_MKkAoTj4wA9oTz-fK0rokgMfuiUWpLt6t=qRXy6vvCh7rg>