Nagios Support Forum

--r4QXMf6/kyF/FvJJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I compiled the latest Nagios 2.0cvs with gcc's profiling and debugging
options. After loading up 10,002 services and launching nagios, I
executed the status.cgi. You can see below that two functions
are taking up the vast majority of runtime. If anything can be
done to improve upon these two functions it would significantly
speed up the responsiveness of the CGI's with large service
lists. =20

$ gprof status.cgi |head
% cumulative self self total
time seconds seconds calls ms/call ms/call name
41.13 3.94 3.94 10002 0.39 0.41 add_service_status
38.83 7.66 3.72 10002 0.37 0.40 add_service
4.28 8.07 0.41 1122533 0.00 0.00 strip

For the same set of services I profiled the daemon.=20

$ gprof nagios |head
% cumulative self self total
time seconds seconds calls ms/call ms/call name
53.58 2.77 2.77 10002 0.28 0.28 xodtemplate_find_serv=
ice
24.95 4.06 1.29 12361 0.10 0.10 add_event
9.09 4.53 0.47 10002 0.05 0.05 add_service
4.84 4.78 0.25 11 22.73 22.73 xsddefault_save_statu=
s_data

I noticed that the intensive functions have linear
list-traversals; at scale they seem to be getting rather
intensive. Perhaps some sort of in-memory index could be built
to optimize that?

Thanks,
-Jason Martin
--=20
This message is PGP/MIME signed.

--r4QXMf6/kyF/FvJJ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: --no-verbose

iD8DBQFBPeBKl2ODWuqVSBMRAhvjAJ9EuH6w7OdaD7ZR2WUdY12j6ohSTwCdEKxr
vmL6OIeczVgGyi9h8FzJu/U=
=xw2E
-----END PGP SIGNATURE-----

--r4QXMf6/kyF/FvJJ--





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]