Highly inefficient for Large Websites

  • Resolved rohitmanglik

    (@rohitmanglik)


    8 years, 3 months ago

    Hi,

    UM creates following cache entries in wp_options table for each user: um_cache_userdata_*.

    These queries have autoload field set to true.

    Wordpress has a native query, which is loaded in almost every page of the site:
    `SELECT option_name, option_value
    FROM wp_options
    WHERE autoload = ‘yes’`

    Now the cached data of each user is loaded everytime a page is loaded. Because of this issue, above query takes 200-250ms in every page load. I am using 32GB RAM Instance in AWS.

    I have a high traffic website so I have to clean the user cache every day and still in just 10-12 hours it starts executing in old time. I am not sure how much I can scale with this issue.

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Support Ultimate Member Support

    (@ultimatemembersupport)

    8 years, 3 months ago

    Hi @rohitmanglik,

    Have you tried to disable cache in Ultimate member -> Settings -> Advanced and “Cache user’s profile data” – OFF?

    Regards.

    Thread Starter rohitmanglik

    (@rohitmanglik)

    8 years, 3 months ago

    Hi,

    It’s already set to off. I am not sure why caching is still happening.

    Screenshot: https://pasteboard.co/GEqCGSi.png

    Thread Starter rohitmanglik

    (@rohitmanglik)

    8 years, 3 months ago

    Also are you sure autoload=true is correct value in WordPress Options for each and every user on site.

    Thread Starter rohitmanglik

    (@rohitmanglik)

    8 years, 2 months ago

    Hi,

    Still waiting for your reply.

    Plugin Contributor Champ Camba

    (@champsupertramp)

    8 years, 2 months ago

    Hi @rohitmanglik,

    Are you running the latest version of UM 1.3.88?

    Regards,

    Thread Starter rohitmanglik

    (@rohitmanglik)

    8 years, 2 months ago

    Yes, I am using 1.3.88 version of UM.

    casinopapa

    (@casinopapa)

    8 years, 2 months ago

    Yes, this is happening for us too. Can this be fixed please?

    Thread Starter rohitmanglik

    (@rohitmanglik)

    8 years, 2 months ago

    Team waiting for your reply!

    Plugin Contributor Champ Camba

    (@champsupertramp)

    8 years, 1 month ago

    Hi Everyone,

    Can you guys update file /ultimate-member/core/um-user.php and change this line in the link?

    https://github.com/ultimatemember/ultimatemember/blob/1.3.88/core/um-user.php#L146

    From
    update_option( “um_cache_userdata_{$user_id}”, $profile );

    to

    update_option( “um_cache_userdata_{$user_id}”, $profile, false );

    And then clear users cache in the UM Dashboard.

    Let me know if this resolves the issue.

    • This reply was modified 8 years, 1 month ago by Champ Camba.
    casinopapa

    (@casinopapa)

    8 years, 1 month ago

    Thanks but won’t this be overwritten in an upgrade? Are you adding this to your core?

    Plugin Contributor Champ Camba

    (@champsupertramp)

    8 years, 1 month ago

    Hi @casinopapa,

    Fixes will be included on the next update.

    Let us know if you’re still encountering issues after you’ve made this small changes.

    Regards,

    jeffreydavisjr

    (@jeffreydavisjr)

    8 years, 1 month ago

    Thank you for this hotfix. My wp_options table was being overloaded with the um_cache_userdata_%. It was crazy. It slowed my website down so much that I had to take it offline. I have about 3000 members signed up on my site so I had 3000 entries in the wp_options table that were autoloaded.

    I deleted them from wp_options manually using “DELETE from wp_options where option_name LIKE ‘um_cache_userdata_%’;

    This thread help me realize that I can do the same through the dashboard…

    Next, I implemented the hotfix as described above and now my website is back as normal!

    The “on/off” switch for caching users doesn’t work. I’ve tested it multiple times. So admins need to implement the hotfix as listed above until the next release.

    Thanks again!

    Thread Starter rohitmanglik

    (@rohitmanglik)

    8 years, 1 month ago

    Good to see I am not the only one suffering here 🙂

Viewing 13 replies - 1 through 13 (of 13 total)

The topic ‘Highly inefficient for Large Websites’ is closed to new replies.