clicommands: Raise memory and exec limits like in Web

[nilmerg]

Had the daemon running for a few hours yesterday and sent me a report for 17k services and thus a PDF with 900+ pages each hour. Didn't notice any buildup in memory. The only thing missing would be a dynamic limit, as it may still crash to produce reports with a large timeframe and a low breakdown. But such a report crashes the UI as well so both parts, UI and CLI, should now be in line and behave the same at least.

fixes #242

[sukhwinder33445]

Unfortunately, it is still throwing a memory exhausted error. I configured the schedule as follows:

1. Created a template with a background image and logo.
2. Created a Service SLA (Icingadb) report using the template with a 4-hour timeframe.
3. Created a minutely schedule of type pdf.
4. Ran the command icingacli reporting schedule run.
5. The schedule runs only twice; the error occurs before the third attempt.

[nilmerg]

You know how this goes now:

• How many services?
• Does this succeed in the UI?
• Are you able to generate this report in the UI in under a minute?
• Did you look at the memory buildup?

[sukhwinder33445]

Sorry, I later noticed that I was still on the old code base when the error occurred.

When using this branch, no error occurs, but the memory usage increases slightly. I have added some logging and i am using the functions memory_get_usage() and memory_get_peak_usage() to monitor it.

I have now rerun the schedule and will monitor it for a while. I will provide an update in a few hours.

Here are the answers to your questions above:

• How many services? 3020
• Does this succeed in the UI? Yes
• Are you able to generate this report in the UI in under a minute? Yes
• Have you looked at the memory Buildup? Yes, it is now increasing slightly, which could be normal.

[sukhwinder33445]

I ran the schedule (minutely) for more than an hour, and the memory usage remains stable between 60 and 63 MB.

[sukhwinder33445]

I could only reproduce the issue using the CLI with the configuration mentioned above. The UI also worked fine with the old code base.

I remember that I had already investigated the problem before and the cause was something else related to css/Pdf-Merge.
At the time, you said that we would not increase the memory because that could not be the real reason.