Comment 0 for bug 1209492

A user can very easily create an infinite amount of logs if they have access to Heat, leading to a very large events table.

 - Create stack with many thousands of AWS::AutoScaling::LaunchConfiguration resources.
 - Update stack changing something that requires replacement of the launchconfiguration in a loop.
 - Every update will involve a 4 events for every resource, delete in progress, delete complete, create in progress, create complete.

Testing with Heat running on a single vcpu VM on my i7 laptop with a slow disk and an intentionally poorly tuned mysql (to amplify mysql performance problems):

With a 10 resource yaml, I was able to create 200 events in 1 minute.
With a 100 resource yaml, I was able to create 500 events in 1 minute.
With a 1000 resource yaml, Heat had problems updating it, and mysql started having issues because the table got fairly large at around 2000 events (working set exceeded innodb_buffer_pool_size so we were disk limited).

After around 3500 evensts, event-list started giving odd json errors.