You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got asked to look at a slow site and while there were a couple issues the biggest was that each get() on the template part was taking 40ms to return (every other query was taking 0.5ms as I'd expect).
This template should have been using get_group(), but was instead using 15 separate get('field_name') functions to query 15 separate fields, looped 30 times... so about 500 of these 40ms queries per page load.
I'm far from a MySQL expert, but indexing meta_id against post_id fixed the performance issues instantly.
I also noticed the query caching seems to of been removed between 2.0 and 2.0.1 for the get_data() function.
Questions:
Would it not make sense to index those fields by default? (Again, beyond my expertise)
What happened to the query caching? (it seems irrelevant to my performance issues, but still it look 'right' before and now it's gone).
This site is multi-site, 13 sub-sites. CPTs have 5-10 fields added, 100s of posts. It's really not "that" big. the biggest table it 10MB, most are smaller.
The text was updated successfully, but these errors were encountered:
jb510
added a commit
to jb510/Magic-Fields-2
that referenced
this issue
Oct 14, 2012
I got asked to look at a slow site and while there were a couple issues the biggest was that each get() on the template part was taking 40ms to return (every other query was taking 0.5ms as I'd expect).
This template should have been using get_group(), but was instead using 15 separate get('field_name') functions to query 15 separate fields, looped 30 times... so about 500 of these 40ms queries per page load.
I'm far from a MySQL expert, but indexing meta_id against post_id fixed the performance issues instantly.
I also noticed the query caching seems to of been removed between 2.0 and 2.0.1 for the get_data() function.
Questions:
This site is multi-site, 13 sub-sites. CPTs have 5-10 fields added, 100s of posts. It's really not "that" big. the biggest table it 10MB, most are smaller.
The text was updated successfully, but these errors were encountered: