Heavy Database Usages.

  • Resolved Dharmesh Patel

    (@dharm1025)


    8 years, 1 month ago

    Hello there,

    Thanks for great plugin.

    I have recently note that, this plugin uses huge database resource. it creates transient(like _transient_aam_post_cache_user_5) for every user and it contain every post types’ post ID. I am using this on complex web application using WP and it creates huge load on database. I have around 4k users and it consume around 400MB space in options table which is too high. I stopped using this plugin. but if you can find solution for this or fix this issue than it will helpful to other users. I just wanted to report issue.

    Thanks,
    Dharmesh

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author AAM Plugin

    (@vasyltech)

    8 years, 1 month ago

    Hi @dharm1025,

    Thank you for the message. Transients are used to cache access settings to posts and terms for each user and it might get out of hands if there are too many users and posts. I will try to find out more balanced solution for larger scale website.

    If it is possible, I’ll like to keep in touch with you so please send me email to [email protected]. It shouldn’t take me more than few days to come up with some options.

    Thank you,
    Vasyl

    Thread Starter Dharmesh Patel

    (@dharm1025)

    8 years, 1 month ago

    Hello @vasyltech,

    Thanks for super-duper fast reply.

    I completely Agreed with you on:

    Transients are used to cache access settings to posts and terms for each user and it might get out of hands if there are too many users and posts.

    I will try to figure out solutions for this in my free time and will notify you if I find anything Useful.

    Thanks,
    Dharmesh

    Plugin Author AAM Plugin

    (@vasyltech)

    8 years, 1 month ago

    Hi @dharm1025,

    Just finished beta version for the improved AAM caching mechanism. So basically now caching is split between different access settings levels.

    Before all cache was stored solely on user level. That is why in your case, with over 4000 users and hundreds of posts, you would have over 4000 cache objects with probably around 100k per each object. That what sums up to 400mb database space.

    With improvements that I’ve added to AAM, this problem is completely eliminated plus I also found a way to fully utilize WP core caching mechanism, so now AAM does less queries to the database.

    You can check the development version here https://downloads.wp.xz.cn/plugin/advanced-access-manager.zip. With few more days of extra testing, these changes are going to be released with upcoming AAM 5.3 version.

    Please let me know if you have any questions.

    Regards,
    Vasyl

    • This reply was modified 8 years, 1 month ago by AAM Plugin.
    Thread Starter Dharmesh Patel

    (@dharm1025)

    8 years, 1 month ago

    Hello @vasyltech,

    Thanks a lot for a beta version. I will test it soon. :+1:

    Regards,
    Dharmesh

    Plugin Author AAM Plugin

    (@vasyltech)

    7 years, 11 months ago

    Hi @dharm1025,

    The latest AAM release should solve your problems.

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

The topic ‘Heavy Database Usages.’ is closed to new replies.