[wp-hackers] Plugin best practices: wp_options and storing custom
otto at ottodestruct.com
Wed Apr 2 21:28:50 GMT 2008
On Wed, Apr 2, 2008 at 4:17 PM, Austin Matzko <if.website at gmail.com> wrote:
> On Wed, Apr 2, 2008 at 5:09 PM, Stephane Daury <wordpress at tekartist.org> wrote:
> > I'm just wondering if the wp_options avenue would lead to a global slow
> > down of the wp install in the long term, since the table is one of the most
> > accessed.
> I think this could happen, because every page load calls
> wp_load_alloptions, which puts all options into the object cache. If
> the options table is huge, this might max out the PHP's memory.
That only gets the options with the autoload column set to "yes".
Other options are only pulled into the cache on an as needed basis.
More information about the wp-hackers