[Resolved] Users Views & Pagination Issue

[Author]

Posts

[ioannisM-2]

Hello,

I am doing some tests to my development website with views and I discovered sth wird. I need to create user profiles and I am testing if it is faster and lighter to use a post view or a user view.

So here is how I did my test: I added 2.741 users to my website and 2.741 posts. Then I created a post view and a user view with exactly the same fields. According to query monitor, the user View needs 3.8 sec to generate the page (196 KB) when the post view needs 6.36 sec (188 KB). Big difference, right?

When I paginated my views sth very strange happened. The user view now needs 2.34 sec from 3.8 sec (188 KB) to create the page when the post view needs just 0.2 sec (13 KB) from 6.36 sec (188 KB)

Why may this is happening? Why the post view has so big difference when it is paginated and the user view remains almost the same? Is this a bug or am I missing a setting?

I am developing a site that may be huge in the future with a lot of users registered to it, so I would like to avoid adding extra content that is not needed. Ideally I would like to use just the user view without adding extra custom fields and custom post type for the creation of the profiles. Is there a way to make the user view faster like is happening with the post view when it is paginated?

If you need to have a look to the live pages the links are:
mydomain.xx/en/view-post-query-test/
mydomain.xx/en/view-post-query-paginated
mydomain.xx/en/view-user-query-test/
mydomain.xx/en/view-user-query-paginated/

[Luo Yang]

Dear Ioannis,

Q1) Why may this is happening? Why the post view has so big difference when it is paginated and the user view remains almost the same? Is this a bug or am I missing a setting?
There are lots of differences between them, the main difference is below
Views uses wordpress class WP_Query to query the posts in database table "wp_posts"
https://codex.wordpress.org/Class_Reference/WP_Query

and uses WP_User_Query to query the users in tatabase table "wp_users"
https://codex.wordpress.org/Class_Reference/WP_User_Query

1) In the database table "wp_posts", there are lots number of columns
https://codex.wordpress.org/Database_Description#Table:_wp_posts
for example column "post_content" is a "longtext" type column,
But in table "wp_users", there are less number of columns, and without "longtext" type column
https://codex.wordpress.org/Database_Description#Table:_wp_users

2) The class WP_Query support cache feature:
https://codex.wordpress.org/Class_Reference/WP_Query#Caching_Parameters
but there isn't cache feature within class WP_User_Query

So it conducts the issues you mentioned above.

Q2) Is there a way to make the user view faster like is happening with the post view when it is paginated?
There are some documents you can refer:
1) shortcode [wpv-view]:
https://toolset.com/documentation/user-guides/views-shortcodes/#wpv-view
Turn on cache feature of Views plugin:
cached (opt): off
Turns off the caching system for the View.
For example: [wpv-view ...cached="on"]

2) How to Use Views Custom Search on Large Sites
https://toolset.com/documentation/user-guides/front-page-filters/how-to-use-views-parametric-search-on-large-sites/

3) Working with Caching Plugins
https://toolset.com/faq/working-with-caching-plugins/

[ioannisM-2]

Oh, that was very clarifying, thank you Luo!