Hi, On 13.09.2013 10:37, CHRISTOPHE M.R. BURNOTTE wrote: > Hello, > > I have a question about Icinga's performance. > > Which gui will have the best performance (in terms of load on a ubuntu > server with apache 2.2.2 and php 5.3.10): the classic Icinga gui (with > cgis) or the Icinga-web gui? > > Might help: number of users +- 100, number of hosts +- 600 (growing to > 2.500), number of services +- 15.000 (growing to 70.000), icinga classic > standard refresh rate: 90s
i'd guess that parsing the status.dat/objects.cache on disk (classic ui) may eat cpu/io on the same host. so if you got a lot of clients, leaving their browser open with automated refresh, this may produce performance problems (recent versions of icinga (1.9.x) got some enhancements in this area, but still). compared to that, if you're using icinga web with a database backend (idoutils), you'll have the sql queries for data fetching (instead of file parsing) which may also generate cpu/io on your system. there's some tuning possible for both guis - status.dat on ramdisk, mysql tuning with more ram and less io. further, you may offload the mysql server to a dedicated box (same goes for icinga web itsself) and reduce the systems performance influence on the icinga core box. thinking of 100 users with 70000 services, i'd say that icinga web is capable of handling such an amount better than classic ui. but that of course depends on the amount of information rendered. icinga web is based on extjs/agavi and causes the client browser to run more javascript than you will encounter with classic ui. on thing further - classic ui uses native "make the loggedin-user a contact for host/service to actually see it" (cgiauth.html on the docs). using icinga web, you may define principals and assign users to specific host/servicegroups and also custom variables. that way, your users just see what they are allowed to see, but not bound to contacts/contactgroups (though, icinga web supports that one too). https://www.icinga.org/about/icingaweb/ i would say, you'll install both on your box. /icinga (classic ui) and /icinga-web (icinga web) and then compare and decide. and make sure you'll have some power in your box as well, if you're planning to keep a local database (idoutils db may be used for icinga reporting too, where icinga web provides an additional cronk widget connecting to the jasper reports soap api). kind regards, michael -- DI (FH) Michael Friedrich mail: michael.friedr...@gmail.com twitter: https://twitter.com/dnsmichi jabber: dnsmi...@jabber.ccc.de irc: irc.freenode.net/icinga dnsmichi icinga open source monitoring position: lead core developer url: https://www.icinga.org ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
