• Resolved will.ph

    (@willph)


    Hi,

    We are trying to implement Redis to our project and observed that the TTFB was at least 4x longer than when Redis is not in use (not the plugin, but the Redis service itself).

    We were advised by AWS Support to ensure the code (the plugin) is adhering to best practices https://aws.amazon.com/blogs/database/best-practices-redis-clients-and-amazon-elasticache-for-redis/

    First, would like to get some form of confirmation that the plugin does follow the best practices as per the link.

    Second, I read on the speed-related topics raised and it seems the Server itself may not be capable enough especially when there are multiple queries being made and Redis is trying to create keys for these. I’m pretty sure this is not a unique issue and would like to get advise on what should be the minimum specs for Redis if the database holds around 20 million rows and being queried multiple times on page load.

    We are not sure if Redis Object Cache Pro would help, so if there’s more information about this also, it would be greatly appreciated.

    Thanks.

Viewing 1 replies (of 1 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    If your TTFB is 4x with Redis enabled, you’re probably not in the same availability zone. I’d check that first.

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