tracker issue : CF-4205491

select a category, or use search below
(searches all categories and all time range)

Potential for thousands of Redis calls every 5 seconds when monitoring sessions with PMT

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Michael F. / ()

Created: 10/21/2019

Components: PMT

Versions: 2018

Failure Type: Performance Issue

Found In Build/Fixed In Build: Update 5 /

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Linux

Vote Count: 0

Problem Description: 

With FusionReactor, you have the ability to track Jedis. This is the library used to create and manage session storage in ColdFusion if you have Redis session management configured, rather than in Memory sessions.

You see that with FusionReactor, there appears to be a function that makes one Redis call for every single session in Redis. This occurs every 5 seconds.

If PMT is removed these Redis calls stop occuring.

With a single session you see there is one redis call every 5 seconds -

with 1000 active sessions there are 2000 redis calls every 5 seconds -

As soon as sessions expire the redis calls stop -

These are the redis calls being made -

Steps to Reproduce:
1. Configure CF 2018 with redis sessions
2. Add FR onto the CF 2018 (optional to give you easy visibility of the Redis calls)
3. Add the CF 2018 to PMT
4. Use Apache benchmark, Apache Jmeter or any other load simulation tool to push a given number of requests that create sessions into CF
5. Observer the active Redis queries

If you require any assistance on FR config email or me personally (I am the technical support engineer for FusionReactor).

Actual Result:
There is a potential for hundreds of thousands of calls to Redis every 5 seconds.
This has the potential to have a big impact on system performance as the number of sessions grows.

Expected Result:
There should not be this many calls to Redis every 5 seconds

Any Workarounds:



This is a duplicate of another bug CF-4205489  Hence, I am withdrawing this bug.  
Comment by Nimit S.
31672 | October 22, 2019 05:43:44 AM GMT