Increase boost maximum memory limits

[YongBoLiu]

Describe the bug
A clear and concise description of what the bug is.

When monitor a very large system, with about 50,000 graphs in RTM. It easy get the errors below,
ERROR PHP ERROR: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 266800 bytes) in file: /opt/cacti/lib/boost.php on line: 1111

To Reproduce
Steps to reproduce the behavior:

1. Monitor 7k hosts.
2. Need to create graphs about 50k.
3. Check the Clog.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.
Please enlarge the boost memory limit as below, and the default value is 1G already.

diff -u -N rtm/cacti/include/global_arrays.php rtm/cacti/include/global_arrays.php
--- rtm/cacti/include/global_arrays.php	2019-03-31 02:45:32.000000000 +0800
+++ rtm/cacti/include/global_arrays.php	2019-05-16 14:06:21.000000863 +0800
@@ -1409,15 +1409,15 @@
 );
 
 $boost_max_memory = array(
-	'32'   => __('%d MBytes', 32),
-	'64'   => __('%d MBytes', 64),
-	'128'  => __('%d MBytes', 128),
-	'256'  => __('%d MBytes', 256),
-	'512'  => __('%d MBytes', 512),
-	'1024' => __('1 GByte'),
+	'1024' => __('%d GByte', 1),
 	'1536' => __('%s GBytes', '1.5'),
 	'2048' => __('%d GBytes', 2),
-	'3072' => __('%d GBytes', 3)
+	'3072' => __('%d GBytes', 3),
+	'4096' => __('%d GBytes', 4),
+	'5120' => __('%d GBytes', 5),
+	'6144' => __('%d GBytes', 6),
+	'8192' => __('%d GBytes', 8),
+	'-1' => __('Infinity')
 );
 
 $realtime_window = array(

[bmfmancini]

That's a good one and will be useful on large systems

I have tested this on 1.2.4 working good so far

I will test more on my end if that helps out cigamit and the dev team to include the expanded memory options

I dont see a reason not to have it as long as you have the hardware to back it up