I see you made some memory improvements. Very nice.

I've been continuing to look at WP memory usage. I've finally come across something that might be of use.

Apparently the add_option function has 4 arguments. The 4th argument is "autoload".

By default I've been using add_option("var", "val") By default that 4th argument is yes. So in order to keep wordpress from autoloading options plugins add, that 4th argument needs to be "no" . The get_option function will then get it on demand instead of loading the added options on startup of every page.

If you could change just this in your plugin, you will save folks a bunch of memory. That way cform options only load on pages they are needed instead of every page.

here is the wordpress add_option def for your convenience.

Josh Baugu

Ya I've learned that the globals var is huge. Especially as more plugins get added. This really comes down to the wordpress folks not trying hard enough to guide plugin authors to a best practice. The wordpress site is unclear on how far back that 4th var goes. You could ask the mailing list or look up the function if you have 2.0.2 somewhere.

They need to teach devs to use that 4th option. Its important when devving a plugin to take into consideration of wether you need them loaded on every page or not. If they would just come up with a best practices page. Maybe someday I will try and piece one together. I'm still learning the wp code base myself though so I'm no expert.

What led me down this path of memory investigation was I got a client who gets 50k uniques a day on his blog. I had to rescue his server as it just couldn't keep up.

Btw, keep up the awesome work. This plugin absolutely rocks. I read that you don't take donations. Just encourage ads. Can they be any type of ad or do they need to be food related?