Register on db or not.

[educostachaves]

I would like to add a feedback. We have recently used this component to do an AB TEST on our website. We have many daily accesses in our home view and because of that we had a problem this weekend.

Our site was unstable, with intermittent drops on AWS. I received many messages from AWS, and for me was a problem to figure out what was wrong. Today we've checked what it was, and we've found in RDS a 100% usage of CPU, and a error shows up on our log: "Too many connections". The AB_Events and AB_Experiments tables had more than 600,000 records, and it blowed up our aws machine this morning.

Soo, this was my fault in not certified me that every access in our website would make an insert in the db, but from the beginning of the implementation, when I've choosed your component and tested how it works, I felt lack of some flag to choose record this in the db or not. It would be an interesting feature for you in the future.

Today we just finished the ABTest on our website, and we've got good results in our metrics.That was really good for our purpose.

[82rules]

I appreciate the feedback and concern. I didn't originally consider throttling DB writes since I wanted to track conversions for every user. I'm all for throttling writes, however I'd like community feedback on how to capture throttled traffic without skewing test results.

[educostachaves]

Interesting, and I agree. Maybe you can do a way to record this on Google Analytics, or an integration with Redis, or a nosql db.

But I think it's not a big problem. For me was a good experience, with good results, and your plugin did what we want.

Well, I will use this again in the future, and I can do an integration that can help you in the future. I will contact you soon, okay?

[82rules]

Sure thanks!