Hi again John,
Sorry for my late replay.
I’ll show you some resource usage information under the following conditions:
- Server: Apache
- PHP: 5.6.10
- WordPress: 4.7.3
- Multisite: yes
- Twenty Twelve 2.2
- IP Geo Block 3.0.2.1
- P3 (Plugin Performance Profiler) 1.5.3.9
- Query Monitor 2.13.4
- Server IP & Memory Usage Display 1.4.0
- Wordfence Security 6.3.6
- WP-Optimize 2.1.1
- WP Crontrol 1.5
- WP Multibyte Patch 2.8.1
Memory usage:
- Before activating IGB: Memory: 36.9 of 1024 MB (4%)
- After activating IGB: Memory: 38.21 of 1024 MB (4%)
CPU usage:
- P3 (Plugin Performance Profiler):

Number of SQL queries:
- Only when blocked:

- All of validation:

I believe that the results show IGB does not spend resources so much. But please consider to the followings:
1. Disabling DNS reverse lookup
DNS lookup spends server resources relatively high. So if you enable “Block by country” on “Front-end target settings” section, please replace HOST to *. It disables to lookup DNS record.
2. Disabling “Record validation statistics” on “Record settings” section.
Writing MySQL tables takes much resources than Reading.
3. Disabling “Record validation logs” or “Only when blocked” on “Record settings” section.
Reducing the frequency of writing MySQL tables would be effective.
I think that No.1 is a suspect of this issue. So I should provide an option to disable/enable DNS lookup in the future release.
Thank you for your posting this issue!
Thanks! I’ve made all three suggested changes to see if that stops the resource limiting that GreenGeeks imposes when I’m trying to edit my site.
Your support is much appreciated.
Hi @burnstuff,
I’m sorry but I have to correct my answer at 1. in the previous thread.
Please copy and paste the followings into your “UA string and qualification” in “Front-end target settings” section.
Google:*,bot:*,slurp:*
spider:*,archive:*,*:FEED
embed.ly:*,Twitterbot:US,Facebot:US
I’d appreciate you if you let me know my suggestion can really help you to solve this issue.
Thanks!
Hi @tokkonopapa,
Just reporting in that after applying the changes you recommended here in this thread, the site is responding faster during editing and I have not seen the limiting from GreenGeeks happening. So I think it’s a good solution. Thank you!
Hi John,
I think “1. Disabling DNS reverse lookup” is the most effective to reduce server’s load. So please try to enable 2. and 3.
And in the future, I’ll equip this plugin with a functionality that enables and disables DNS reverse lookup.
Thank you for your feedback!