[wp-trac] [WordPress Trac] #39605: Possible wp_options autoload field optimization
WordPress Trac
noreply at wordpress.org
Tue Jan 17 19:22:38 UTC 2017
#39605: Possible wp_options autoload field optimization
--------------------------------+------------------------
Reporter: danielkanchev | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: Options, Meta APIs | Version: trunk
Severity: normal | Resolution: duplicate
Keywords: | Focuses:
--------------------------------+------------------------
Comment (by danielkanchev):
@swissspidy and @rmccue thanks for the information and the links to the
other tickets. I checked the other tickets and I have one question:
How many rows does the wp_options table need to have maximum to be
considered "normal"?
In #14258 @pento wrote the following:
>Even assuming a ludicrously massive wp_options table of 5000 rows
So I am wondering what is considered to be the maximum number of rows
above which the wp_options table becomes bloated.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/39605#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list