Performance problems

Hi,

I sought for finding node of the problem, here is joined my report :

This is the algorithm of the widget-categories, it is the way for walking through the tree which generates the problem.
Each node is got separately and issues a UAM request for validation of access (192 accesses and 80% of resources of the whole of the post display).

Nevertheless there are sometimes other UAM internal loops which could avoid to call directly a request to the DB, so a solution is : before loop issue a more global request to create an array into which data could be found.

But they are inside the 10% of problems remaining.

Best regards

Trebly
_________________________________________________________
Report which shows to origin of the overload of resources

debug-from-logs-b61206-1-notes-2-UAM_queries

________________________________ Query type ______________________
Repeated 192 times on various wp_term_relationships.term_taxonomy_id IN (111)
IN (…) various selections
elementary request is between 0.003 average near 0.015s

the whole uses :
Queries in filter (UAM && WP_Query->get_posts()
wp-includes/query.php:3655 : 192 2,3712
Queries in filter (UAM All) : 512 2,7610

on Total Queries for page : 671 2,9845

The Widget : categories is the origin of 80% of time used
wp_dropdown_categories()
wp-includes/category-template.php:416
WP_Widget_Categories->widget()
wp-includes/widgets/class-wp-widget-categories.php:83

It is 80% of the problem of DB resource used by UAM
repeated selection for drop-down widget of the categories
_________________________________________________________
SELECT wp_posts.*
FROM wp_posts
LEFT JOIN wp_term_relationships
ON (wp_posts.ID = wp_term_relationships.object_id)
WHERE 1=1
AND ( wp_term_relationships.term_taxonomy_id IN (111) )
AND wp_posts.post_type = ‘post’
AND ((wp_posts.post_status = ‘publish’))
GROUP BY wp_posts.ID
ORDER BY wp_posts.post_date DESC

The call stack of this request is :
__________________
WP_Query->get_posts()
wp-includes/query.php:3655
WP_Query->query()
wp-includes/query.php:4050
get_posts()
wp-includes/post.php:1595
UserAccessManager->_getTerm()
wp-content/plugins/user-access-manager/class/UserAccessManager.class.php:1856
UserAccessManager->showTerms()
wp-content/plugins/user-access-manager/class/UserAccessManager.class.php:1921
apply_filters(‘get_terms’)
wp-includes/plugin.php:235
get_terms()
wp-includes/taxonomy.php:1235
wp_dropdown_categories()
wp-includes/category-template.php:416
WP_Widget_Categories->widget()
wp-includes/widgets/class-wp-widget-categories.php:83
WP_Widget->display_callback()
wp-includes/class-wp-widget.php:377
dynamic_sidebar(‘sidebar-1’)
wp-includes/widgets.php:738
load_template(‘~/wp-content/themes/Twentythirteen2/sidebar-main.php’)
wp-includes/template.php:572
locate_template()
wp-includes/template.php:531
get_sidebar(‘main’)
wp-includes/general-template.php:122
load_template(‘~/wp-content/themes/Twentythirteen2/footer.php’)
wp-includes/template.php:572
locate_template()
wp-includes/template.php:531
get_footer()
wp-includes/general-template.php:84

Hi,

Complements :

When UAM is not running there are no more requests to database.

So it seems that the problem is that when the basic function of WP : “wp_dropdown_categories” is called, at each node when attached posts are accessed the UAM hook checks the access group launching the db query above (previous comment).
When this is done by the core there is no significant access to database, but when UAM is used each node leads to an heavy query (average of 3 per node it seems).

I think that it should be necessary for categories and others list produced to have a global query for visibility and a comparison of array or objects to answer for access.
I have no idea how to perform this but for now I cannot display such list of objects when I use UAM.

May be other widget for categories, using ajax, will be less voracious in resources.

Best regards

Trebly

You could try the newst version at https://github.com/GM-Alex/user-access-manager

Feedback would be great.

Notes

• The object type ‘category’ at the uam_accessgroup_to_object table will change to ‘term’. So you need to update the database if you want to use the test version and change it back if you are done with testing.

Should be better with the latest version.

Hi,

Partial test (no statistics comparison) done today : everything OK, there are no more excessive resources used.

Thanks

Best regards

Trebly