Opened 9 years ago
Closed 9 years ago
#36436 closed enhancement (invalid)
wp_options table size - cached RSS feeds
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | |
| Component: | Database | Keywords: | |
| Focuses: | Cc: |
Description
Hello, I was analyzing my wp_option table size and noticed some enormously big "transient_feed_*" rows (with news-like serialized content). After fresh install my WP database takes up 606 kB, wp_options consumes 425 kB of it, and three "fransient_feed_*" rows holds up to 350 kB of that table - more than 80 percent!
I finally tracked saving of those transient to class-feed.php file ... so it seems like automated action when fetching any RSS feed.
I know they are transients ... but is it performance-wise to hold 245kB of text in one table column? I don't know, actually, so I ask.
Change History (1)
Note: See
TracTickets for help on using
tickets.
Thanks for the ticket, @mklusak!
There's no performance concern with having this data in the column - the TEXT column is designed to store large blobs of text. It doesn't affect the speed of queries, as InnoDB is smart enough to skip over those blobs of text when scanning the table.
It doesn't affect WordPress performance, either - the feed transients are not automatically loaded when WordPress loads, so they don't cause unnecessary data transfer between WordPress and MySQL.