BoldMinded

Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: CSM drastically slows down my site - can barely access it.

Status Resolved
Add-on / Version Custom System Messages
Severity Critical
EE Version 24

Jessica Dooley

Apr 29, 2013

Hi there,

I’ve had this happen now on two different sites (am building these simultaneously).  These two sites are very similar, and the one thing that I can think of that is significantly different from other sites I’ve built recently with same EE version, addons, (basic default install etc) is that these two are both using the core search module.

With CSM installed (even with default settings), any basic action will spin for several minutes, accessing either the frontend or backend.  I tested my site disabling one extension at a time to verify which was the culprit… 

For example:

BENCHMARKS (backend with CSM disabled/uninstalled)
Loading Time: Base Classes   0.0023
Total Execution Time   0.0703
Controller Execution Time ( Addons Extensions / Index )  0.0682

BENCHMARKS (backend with CSM installed)
Loading Time: Base Classes   0.0023
Total Execution Time   111.5472
Controller Execution Time ( Addons Extensions / Index )  111.5451


BENCHMARKS (frontend with CSM disabled/uninstalled)
Loading Time: Base Classes   0.0143
Total Execution Time   0.3184
Controller Execution Time ( Ee / Index )  0.3040

BENCHMARKS (frontend with CSM installed)
Loading Time: Base Classes   0.0017
Controller Execution Time ( Ee / Index )  104.5093
Total Execution Time   104.5112


*NOTE: I’ve noticed that it’s really bad when I first install/enable CSM - and then it get’s worse and worse each time I try to access anything…


EE Version: 2.5.5 - Build Date: 20121220

CSM Version: 2.5

Installed Modules/Extensions:
*see screenshots attached

Any thoughts on why this would be happening?

#1

BoldMinded (Brian)

Sorry this is happening. Can you go to line 155 of ext.system_messages.php and comment out this line:

// session_start();

Just add the // in front of it, then see what happens.

#2

Jessica Dooley

Thanks for the quick response!

That helped the backend, but the frontend is still spinning:

BENCHMARKS
Loading Time: Base Classes 0.0025 Controller Execution Time ( Ee / Index ) 118.7167 Total Execution Time 118.7194

#3

BoldMinded (Brian)

Oh, scroll down to line 180 and do the same thing.

#4

BoldMinded (Brian)

Instead of commenting out those lines, put an @ in front, e.g.

@session_start();

Let me know if that still causes the slow down.

#5

Jessica Dooley

Sweet, that seems to have fixed it!

BENCHMARKS
Loading Time: Base Classes 0.0025 Controller Execution Time ( Ee / Index ) 0.1072 Total Execution Time 0.1099

Thank you!

#6

BoldMinded (Brian)

So was it the @ or commenting out the line entirely?

#7

Jessica Dooley

I tested both, and am getting about the same load time for each. Have it set with @ now and all seems good…

#8

Jessica Dooley

Sorry, I take that back… things were starting to slow down again so I commented out those lines instead, and for now it’s better.

With the @: Loading Time: Base Classes 0.0024 Total Execution Time 83.1118 Controller Execution Time ( Addons Extensions / Extension Settings ) 83.1096

Commented out: Loading Time: Base Classes 0.0043 Total Execution Time 0.0726 Controller Execution Time ( Addons Extensions / Extension Settings ) 0.0685

#9

Jessica Dooley

Note - I hadn’t made this change on the other site with the same issue, and our client called and was making some changes, I was still having the loading issue with the developer login, but they weren’t having any issues at all with the editor login (minimal access). I’ve tested it and the site runs fine with the editor login…

Something to do with the difference in addon permissions? The editor login does not have permissions to Extensions.

#10

BoldMinded (Brian)

This add-on won’t be affected by member group permissions, it only processes on the front-end. The root cause of the issue is the server can’t write to a folder where it saves the session data, usually /tmp

#11

BoldMinded (Brian)

I take that back, its not necessary a folder write issue, its a file lock issue. If the add-on works fine without it then keep using it that way. I’ll see if other people report similar issues and if they do I’ll remove that line, but I’ve had that in there for months with no reports like this to date.

http://stackoverflow.com/questions/1914242/problem-with-function-session-start-works-slowly/1914266#1914266

#12

Jessica Dooley

Ok that sounds good, I’ll let you know if I run into any other issues but for now commenting those lines out seems to have fixed it 😊

Thanks for your help and explanation!

Login to reply