Title: Memory usage Last modified: August 22, 2016 --- # Memory usage * [diegonofx](https://wordpress.org/support/users/diegonofx/) * (@diegonofx) * [11 years, 7 months ago](https://wordpress.org/support/topic/memory-usage-3/) * Hi, I realized a huge increment in our memory usage since I installed the CTA plugin. I love the plugin and I want to use it for a project with a big amount of content, this means maybe more than 200 or 300 CTA’s online at the same time. So far I have 26 CTA’s online and the memmory usage was already two times incremented due the plugin needs, now it is on 350MB. Is this amount of memory usage normal? And if it is, this means that my plan to use this plugin in this specific project is not viable? Thanks! * [https://wordpress.org/plugins/cta/](https://wordpress.org/plugins/cta/) Viewing 6 replies - 1 through 6 (of 6 total) * Plugin Author [David Wells](https://wordpress.org/support/users/davidwells/) * (@davidwells) * [11 years, 7 months ago](https://wordpress.org/support/topic/memory-usage-3/#post-5387824) * What memory usage are you referring to? * Where do you host? * Plugin Author [Hudson Atwell](https://wordpress.org/support/users/adbox/) * (@adbox) * [11 years, 7 months ago](https://wordpress.org/support/topic/memory-usage-3/#post-5387853) * The increase in memory usage is due to the plugins usage of wordpress ajax on every page load. * This is due that wp-admin ajax calls are never cached, and can’t be, so we can pull dynamic data out of the database. * Our cta variation loading system as well as the impression tracking system use the wp-admin ajax. So this will load 2 backend calls per frontend visitor wherever a call to action is. (Should never be more than two though I don’t believe). * Unfortunately due to caching systems we won’t be able to fix this until we begin storing cta impression & tracking data off site on our own servers. * To improve load times and cut back on server resource usage you can disabled split testing in your global settings and this will only load the first variation on calls to action every time, cutting out the need for half of the ajax calls to the backend. * Thread Starter [diegonofx](https://wordpress.org/support/users/diegonofx/) * (@diegonofx) * [11 years, 7 months ago](https://wordpress.org/support/topic/memory-usage-3/#post-5387885) * Thanks Hudson this make sense. I will try to continue withou A/B Testing in every post and just leave it for special CTA. * Thread Starter [diegonofx](https://wordpress.org/support/users/diegonofx/) * (@diegonofx) * [11 years, 7 months ago](https://wordpress.org/support/topic/memory-usage-3/#post-5388003) * Hi, * Since the ajax calls are never cached, does the plugin release or free the memory after each call? * I’m asking this because if it does free/release the memory, then I think we have another issue at hand since in our logs we see the plugin always asking for more memory, no matter how much we set initally. * Granted, it’s not asking for more than 100kb of data but still … * I tried to erase the B vesions in all my call to actions and deactivated the A/B testing, but still it ask for extra memory. * Thanks! * Plugin Author [Hudson Atwell](https://wordpress.org/support/users/adbox/) * (@adbox) * [11 years, 7 months ago](https://wordpress.org/support/topic/memory-usage-3/#post-5388007) * It’s the calls to the wp-admin. * After one PHP session/visit the memory usage should destroy itself. * So there should be a hard limit to how much memory calls to action can use and all of this memory usage should be due to ajax loading wp-admin to run an ajax call. * With split testing disabled from the global settings area these ajax calls should be limited to two per visitor wherever there is a call to action. * We are running the plugins successfully (with split testing off) on a site with more than 700,000 hits a month. If we turn split testing on it bogs down. Off it works fine though. * Plugin Author [Hudson Atwell](https://wordpress.org/support/users/adbox/) * (@adbox) * [11 years, 7 months ago](https://wordpress.org/support/topic/memory-usage-3/#post-5388008) * Also to disable split testing you will not have to delete your other variations, but only toggle a setting in the wp-admin global settings area. Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘Memory usage’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/cta_a5a5a5.svg) * [WordPress Calls to Action](https://wordpress.org/plugins/cta/) * [Frequently Asked Questions](https://wordpress.org/plugins/cta/#faq) * [Support Threads](https://wordpress.org/support/plugin/cta/) * [Active Topics](https://wordpress.org/support/plugin/cta/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/cta/unresolved/) * [Reviews](https://wordpress.org/support/plugin/cta/reviews/) ## Tags * [memory usage](https://wordpress.org/support/topic-tag/memory-usage/) * 6 replies * 3 participants * Last reply from: [Hudson Atwell](https://wordpress.org/support/users/adbox/) * Last activity: [11 years, 7 months ago](https://wordpress.org/support/topic/memory-usage-3/#post-5388008) * Status: not resolved