totally froze up my AWS instance

Seems weird. What size of instance were you running it on?

A Micro which is the smallest. I was able to get it running by switching to a larger instance. This has never happened with other plugins, and I run ton of things on that particular micro without issue. I just can’t seem to figure out what is going on with this plugin beyond a few rest calls to Twilio. What’s with the giant resource drain? Got to be refinements and tweaks that can be implemented here. I actually wonder if there is a memory leak situation.

Could be a memory leak, though I’ve only heard this a couple times (20K+ downloads later). It does hit admin-ajax.php immediately on page load (to avoid caching issues). My energy is being put into Version 2.0, which takes the load completely off the server, onto a third party service. Not sure when that release date will be yet.

Well, it’s very cool you are so responsive, and it’s nice to hear about a 2.0 version coming along. I’m really not pleased with this memory issue; however, the design and the features (looks great on mobile, integration with Twilio, has ability to schedule…) are very well done. Despite the performance shortcomings, as long as it doesn’t crash my bigger instance, I’ll still stick with this plugin just because it is so well done. Now if it ends up crashing my bigger instance, then I’ll have to steer clear. But if it remains working, then I think we’ll be in a good spot.

Thanks and glad to hear you stick with it!

You won’t be disappointed when 2.0 comes out!