• Vimal Roy

    (@vimalroy08)


    Dear @tillkruess and Redis Object Cache Support Team,

    We are currently using the Redis Object Cache plugin on our WordPress website, a high-traffic multilingual news platform that primarily focuses on cryptocurrency and blockchain-related content. Our website has over 56,000 posts in total, available in 8 languages, and we publish 30-50 new articles daily. Our team of 20-30 users, including publishers from various regions, actively works on the website simultaneously—creating, updating, publishing, and translating content.

    Recently, we have been encountering several persistent issues that are impacting our site’s performance, detailed below:

    1. Error Establishing Redis Connection: We frequently receive errors such as RedisException: read error on connection to /run/redis/redis-server.sock. This typically occurs when clearing the cache for the first time each day, after periods of inactivity, or when creating new posts. Despite having ample resources available, Redis seems unable to handle the connections consistently.
    2. Socket Errors and HTTP 500 Errors: We are experiencing repeated socket read failures and occasional HTTP 500 errors directly linked to Redis performance issues. These disruptions significantly affect our website’s availability and overall user experience.
    3. Plugin-Related Issues:
      • WPML: Our website relies heavily on WPML for multilingual functionality, and we’ve noticed that Redis interactions frequently coincide with performance slowdowns when WPML is active.
      • Yoast SEO: Essential for our SEO strategy, Yoast is also generating a high number of Redis requests, which could be contributing to the connection issues.
      • Wordfence: Security is a priority for us, and Wordfence is critical. However, it appears to be interacting with Redis in a way that may be contributing to the overall load.
      • Post Views Counter: We are currently evaluating whether this plugin is necessary, but it is also making frequent requests to Redis, adding to the load.

    PFA :-

    https://www.awesomescreenshot.com/image/50430705?key=30ccd35b8b9f97b73d55606783f2019b
    https://www.awesomescreenshot.com/image/50430704?key=cba43d0b0718defbee585926508fb7e4

    Given these challenges, we are seeking your expertise and guidance. Are there any known fixes, configurations, or optimizations within the Redis Object Cache plugin that could help mitigate these issues? Specifically, are there ways to reduce or optimize the load generated by these plugins or exclude certain requests to Redis?

    If there are any previously discussed solutions or recommendations that you could direct us to, it would be greatly appreciated.

    Thank you in advance for your assistance. We look forward to your insights on resolving these issues and enhancing the stability and performance of our Redis setup.

    Best regards,

    Vimal Roy

    • This topic was modified 1 month ago by Vimal Roy.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • I have the same issue… it’s happening way too often.

    Plugin Author Till Krüss

    (@tillkruess)

    With a team of 20-30 people you might want to consider using Object Cache Pro instead.

    As for read error on connection and 500 errors, that’s your Redis Server not responding in time, are you monitoring Redis Server? What do the CPU charts look like?

    I’d need to see Redis logs to tell you which commands are failing and why.

    Consider setting these, that might help with timeout:

    WP_REDIS_DISABLE_GROUP_FLUSH=true
    WP_REDIS_SELECTIVE_FLUSH=false
    Thread Starter Vimal Roy

    (@vimalroy08)

    Hello @tillkruess ,

    Thank you for your prompt response and for the suggestions provided.

    To clarify, our team includes a mix of authors, editors, and administrators, but only about 7-10 people are actively engaged in creating, translating, editing, and publishing articles at any given time. While we have multiple roles on the site, the actual number of concurrent users performing content-related tasks is smaller, though they are often working simultaneously.

    We appreciate the configuration recommendations, specifically the use of:

    • WP_REDIS_DISABLE_GROUP_FLUSH=true
    • WP_REDIS_SELECTIVE_FLUSH=false

    However, we noticed in the Redis Object Cache plugin guide on GitHub that WP_REDIS_SELECTIVE_FLUSH is listed under Unsupported configuration options, with a note that options in this category may break without notice in future releases and won’t receive support from your team.

    Our questions are as follows:

    1. Stability and Future Compatibility: Given that WP_REDIS_SELECTIVE_FLUSH is marked as unsupported, could you please provide insight into any potential risks associated with adding this constant? Specifically, are there any known stability issues, performance implications, or long-term concerns we should be aware of?
    2. Redis Server Monitoring: We understand that the Redis Server not responding in time is a core issue, and we are actively monitoring its performance. However, could you please advise on what specific Redis logs or command failures we should be focusing on to better diagnose and address these connection errors?
    3. Object Cache Pro Consideration: We are open to exploring Object Cache Pro if it can provide enhanced stability and performance for our setup. Could you share more details on the expected benefits, particularly in the context of our high-traffic, multilingual environment?

    Additionally, we have attached a document containing Redis logs that capture various warnings and errors, including RedisException events that are affecting our site. You can access the logs here. We would appreciate it if you could review these logs and provide any insights or recommendations based on the issues highlighted.

    Your guidance on these queries would be invaluable as we work to optimize our Redis setup and mitigate these ongoing performance issues.

    Thank you once again for your continued support, and we look forward to your feedback.

    Best regards,

    Vimal Roy

    Plugin Author Till Krüss

    (@tillkruess)

    Correct, WP_REDIS_SELECTIVE_FLUSH is unsupported and off by default, I just wanted to make sure you have it set to false.

    As for Redis Server monitoring, there are various tools out there like New Relic and Datadog, if you’re already monitoring your infrastructure with a tool, they might have Redis monitoring as well.

    Thanks for the sharing the logs, it’s not enough to go on, since the issue is Redis not responding at all or in time.

    Object Cache Pro Consideration: We are open to exploring Object Cache Pro if it can provide enhanced stability and performance for our setup.

    That’s exactly what is does, in that order 🤙

    Thread Starter Vimal Roy

    (@vimalroy08)

    Hello @tillkruess

    Thank you for your response and for the clarification.

    To confirm, we have set WP_REDIS_SELECTIVE_FLUSH to false in the wp-config.php file as recommended.

    Regarding the monitoring tools, we are currently not using New Relic, Datadog, or other specific Redis monitoring tools. While we do monitor the website, server load, and related metrics, we have not implemented any dedicated monitoring for Redis itself.

    Upon reviewing yesterday’s logs, we identified two occurrences of 500 errors related to Redis in the access logs. We have cross-referenced these with the corresponding web server error logs and Redis error logs. For your reference, I have shared the details of these errors in the following Google Docs link: View Logs.

    Since the previous logs were not sufficient for further analysis, we hope that these newly shared logs provide more clarity on the issues we are experiencing. Please review them and let us know your feedback or any additional recommendations.

    If you need anything more or any other specific information/logs, please let me know.

    Thank you once again for your continued support.

    Best regards,
    Vimal Roy

    • This reply was modified 3 weeks, 2 days ago by Vimal Roy.
    Plugin Author Till Krüss

    (@tillkruess)

    The errors socket error on read socket and read error on connection are timeouts (or high latency responses).

    Can you post the output of redis-cli SLOWLOG GET?

    Thread Starter Vimal Roy

    (@vimalroy08)

    Dear @tillkruess ,

    Thank you for your insights on the timeout issues. As requested, I have gathered the output from redis-cli SLOWLOG GET, which you can access through the following link:

    View SLOWLOG Output.

    Could you please review the logs and provide any further recommendations on how we might reduce or fix these timeout errors? We are particularly interested in understanding if there are any specific Redis configurations or optimizations we could implement to mitigate these socket timeouts and high-latency responses.

    Your guidance on resolving this issue would be greatly appreciated, as the timeouts are affecting our website’s stability and performance.

    Thank you once again for your continued support.

    Best regards,
    Vimal Roy

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.