MPM: Worker vs Event ... и создание с помощью профилей CloudLinux EasyApache
Форум
  1. Forums
  2. CloudLinux and Control Panels
  3. CloudLinux and cPanel
  1. Shannon Plaquet
  2. Tuesday, 13 June 2017
  3.  Subscribe via email
So, I'll preface this question with my CloudLinux/Linux knowledge level. It's kind of how I describe most of my clients... "Typically knows enough to get the job done, but also enough to be dangerous." With that being said, I realize that I don't know it all and am constantly learning. ...usually from research and then from trial and error. I'm not going to take anything personally. I'd love some insight from the pros out there on these questions.

From the research that I've done, it sounds as though MPM_Event can handle more threads than MPM_Worker. If that is the case, why is it that Worker is compiled within the CL Profiles vs Event? And secondly, why don't really see much reference to Event within the CL docs?

So I had MPM_Event installed on a new CL box for a client. It just wasn't performing up to par and it kept having various hiccups. I updated and compiled with MPM_Worker. The performance issues seemed to have been fixed which is wonderful, but left me with more questions.

Since I went with Worker, I thought that I'd play it safe and recompile with a customized CL profile in EasyApache4. Unfortunately, I cannot figure out how to fix the error "This profile includes the following packages that are not supported on this server: php56-php-debuginfo". I read up on cPanel's documentation and see that (if I remember this correctly) only 1 DSO can be installed at a time, and that is why I'm seeing that error. I tried to follow their guide on removing, but I'm not able to figure it out. I have php5.5, 5.6, 7.0, and 7.1 on that box. I also have lsapi as my php handler, but cgi and suphp is also listed. What do I have to remove in order to build one of the default CL profiles and remove that error?

When provisioning with a default CL profile, does CL have a preference/recommendation of ZendGuard vs OpCache? If there is a suggested choice, are there any documents that explain the benefits of one over the other with a CL install? I'm confident that the answer is out there, but I could only find articles that were mostly pre 2016. For that reason, I didn't feel 100% comfortable reading them and believing that they were 100% accurate today in 2017.

And I don't want to get too far off topic, but can mod_PageSpeed be included at some point in the builds? I can set it up easily enough, but it's one of those mods that I'd feel 1000x more comfortable if the team at CL tweaked things up for an auto/included installer. I'd feel a million times better that everyone was playing nicely with everyone else (referring to scripts, mods & extensions).
Attachments (1)
Rate this post:
Accepted Answer
  1. 15.06.2017 12:06:17
  2. # Permalink
Bogdan Accepted Answer
Posts: 709
Joined: 26.06.2013
0
Votes
Undo
Hi,

I have clarified questions with our developers and here are answers:
1. We follow same EA4 profiling as cPanel does, overall it's standard+mod_hostinglimits+mod_lsapi . If cPanel will add a profile with mpm event then we will provide it also with our package.

2. The php56-php-debuginfo is really obsolete package, we will remove it from ea-profiles-cpanel package and most probably will release to beta today.

3. I worry there are no recommendations about opcache and ZendGuard.

4. Adding mod_pagespeed also depends mostly from cPanel, if they add it - we will follow them and to the same.
  1. 15.06.2017 21:06:40
  2. # 1
Shannon Plaquet Accepted Answer
Posts: 8
Joined: 05.06.2017
0
Votes
Undo
hah. well allrighty then. maybe i don't feel so silly for asking the question then ;)
  • Page :
  • 1


There are no replies made for this post yet.
Be one of the first to reply to this post!
гость
Submit Your Response
Upload files or images for this discussion by clicking on the upload button below. Supports gif,jpg,png,zip,rar,pdf
• Insert • Remove Upload Files (Maximum File Size: 2 MB)
Captcha
To protect the site from bots and unauthorized scripts, we require that you enter the captcha codes below before posting your question.