Jump to content

Forum slow with CJ Duplicate Member Logger Enabled

  • CJ Duplicate Member Logger 1.0.9 CJ Duplicate Member Logger 1.0.8 Closed Bug


Now there is another issue with your app. I've seen our forum becoming really slow to navigate or do anything for the past few days to the point that it became unresponsive today*. I started debbuging the issue and the problem was gone by disabling your app. Now our forum is back up to its normal speed.

We have a very active forums, with over half a million registered users, and we've seen similar issues in the past where an app/plugin would work fine in testing environments and smaller forums, but would cause performance issues in a forum with high traffic such as ours.

* It started giving me 502 errors. See below:

access log:

[redacted] [16/Jul/2016:05:32:21 -0300] "GET / HTTP/1.1" 502 568 "http://forum.clubedohardware.com.br/" "Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36"

error log:

2016/07/16 05:32:21 [error] 11121#0: *11188 upstream sent too big header while reading response header from upstream, client: [redacted], server: forum.clubedohardware.com.br, request: "GET / HTTP/1.1", upstream: "fastcgi://", host: "forum.clubedohardware.com.br", referrer: "http://forum.clubedohardware.com.br/"


User Feedback

Recommended Comments

I will have to dust off a copy of ips 4.1.12 or older, as 4.1.13+ is impossible to use atm to develop on (the database creator, in the dev center is broken). I also see now about the issue with the options not showing for you too...the database creator in the dev center didn't actually add in the fields for the moderators for the upgrade/install routine. automation and hand holding is great when baked into a software, its a nightmare when it is broken down. 

for this problem, i think it is related to the fields not being added in. as i changed the way it determines if it should run or not (like there is no point to always running it, like you are experiencing the excessive server load), so it should be checking when you first login/go to the site, and then it shouldn't check again till you login/go back to the site,etc. I'll switch it back to the way i had it, to avoid this issue (as i'm assuming this is relatively new, since the last few updates?), and get the other bugs fixed on it (like the missing language strings).

Link to comment
Share on other sites

What you say makes total sense. I only started experiencing this issue this week, which I assumed it was due to my internet connection, but it kind of matches the day we installed 1.0.8 and I didn't make the connection... Take your time, it is better to get this right to rushing a new version out. Cheers!

Link to comment
Share on other sites

  • Create New...