Linux SHA256: bc8d8ca3d2a102f878d619e2b616f8553dcf821dfd28ca93873dc0c7dd96a99c
Linux md5sum: 617ff979775a8ecd34a5dde9ba193341
So, that was a ride... In testing our new Rules feature worked a treat. In practice, not so much. Most servers (ie, not mine) can't cope with loading the rule set, even if we break it down to smaller chunks, when processing multiple devices. What to do? What to do? Well we've taken a small step back. Rules still exist as a feature, and they still work a treat. But instead of inserting 100,000 Rules into the database, we've split them up into four distinct files and implemented them as code only. Hence, no loading all 100,000 Rules, decoding JSON and running them against a device. Now we just load the files and run the statements. Much, much faster and more memory efficient. No load on MySQL, and hence the CPU also drops. No populating a massive recordset and hence the memory drops. The not so good thing - these are no longer editable in the GUI. But it's not the end of the world. You can still make Rules as you see fit and they will be run after the "default" rules (those in code), hence you can override the "default" rules. So we don't loose much, but we gain a LOT of performance. We also added a few new Rules for Mac Models.
Apologies for any inconvenience this caused anyone.
|Open-AudIT||Bug||Rules||Move most rules into code to improve performance.|
|Open-AudIT||Improvement||Rules||Add some new Rules for Mac Models.|