On 13.09.2013 14:18, Christophe HAEN wrote: > To comment on what Michael F. said, the problems indeed showed up when > several users were keeping the classic cgi page opened. > Actually, it even sometimes impacted the performance of the icinga > core itself and the latency was going high.
that's generally something one does underestimate in setups. monitor the apache access.log with e.g. check_logfiles and count the requests - and then look at the size of status.dat/objects.cache and calculate the magic number of cpu cycles ;-) i had that problem in my previous workplace, and ramdisks did not help much (physical hardware, proliant g7 with fast raid1 controller below). > Since then we have a much more powerful machine so the problem does > not appear anymore. But at the time, going for the icinga web > interface and outsourcing the DB on another server did the trick obviously one might not like icinga web in the first place. but for removing the load of querying for data from your actual monitoring core, it's a great deal. and with 1.9.x you'll get the socket queue in idoutils too, which results in asynchronous non-blocking database updates too, allowing you to offload the ido2db daemon as well (if you fear the cpu load on the box). the icinga2 ido component acts asynchronous too, and maybe you'll give that one a shot on your test boxes (and put it into production later on). it still writes status.dat/objects.cache too if the compat component is loaded. that's just for "test it while it lasts" mention i do all the time now ;) regarding the sparc 440mhz - well that's low end, just as embedded hardware. noone expects a mysql cluster running on pi's (or do they?). having an rdbms as backend for icinga web and reporting, you'll get more complex data aggregation capabilities left to the rdbms itsself fetching the output afterwards. example - sorting in memory on browser call is evil. classic ui / cgis do that - they parse the files into memory and operate on that. that's quite the same you need to do with livestatus json in your php application, sort it like beckham on-call. i'm obviously more of the database guy (there's a reason why idoutils got oracle/postgresql support), but i do see the benefit of it in large scale systems having the necessary power as backup available. consider a current hardware platform (or dedicated esx hosts) assigning 12+ cores and 64gb ram to your box, and give mysql 50% memory (and other tuning tricks, see the wiki). you'll likely have fun with it. more than letting a cgi parse a file on disk and do some aggregation and sorting with it. but that's merely nitpicking - given the amount of 15000-70000 services i'd say icinga1.x master/slave setup (and icinga2 standalone later) plus icinga web. for the small sparc cpu, use the native old classic ui and small sizing. but obviously you could tune mysql a bit (or get a recent version, iirc that was 5.0.x and ancient. 5.5.x in debian wheezy scales well). jm2c, michael > > > 2013/9/13 Carl R. Friend <crfri...@rcn.com <mailto:crfri...@rcn.com>> > > On Fri, 13 Sep 2013, Alexander Wirt wrote: > > > Christophe HAEN schrieb am Friday, den 13. September 2013: > > > >> Hi, > >> > >> in our case, the cgi interface was implying a heavier load than the > >> icinga-web one. > > That is probably only the case if you need idoutils. If you > don't use > > idoutils, -classic should be lighter. > > If the OP wants to use Web, he's going to have to use IDOutils. > > I haven't seen anything published concerning performance, but when > I loaded Icinga-Web onto a 440MHz Sun SPARC system with 1 GB of main- > store it pretty well crushed the machine by immediately driving it > deeply virtual. That's with 15 hosts and 51 services (the number of > services is misleading -- I have a lot of "services" that actually > monitor several parameters at once). Classic runs on it just fine. > > Cheers! > > +------------------------------------------------+---------------------+ > | Carl Richard Friend (UNIX Sysadmin) | West Boylston > | > | Minicomputer Collector / Enthusiast | Massachusetts, > USA | > | mailto:crfri...@rcn.com <mailto:crfri...@rcn.com> > +---------------------+ > | http://users.rcn.com/crfriend/museum | ICBM: 42:22N > 71:47W | > +------------------------------------------------+---------------------+ > > > ------------------------------------------------------------------------------ > 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 > > <http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk> > _______________________________________________ > icinga-users mailing list > icinga-users@lists.sourceforge.net > <mailto:icinga-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/icinga-users > > > > > -- > Christophe HAEN > CERN PH-LBC 2/R022 > Phone : +41 (0)2 27 67 31 25 > Mobile : +41 (0)7 64 87 88 57 > > > ------------------------------------------------------------------------------ > 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 -- 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
