Zend opcache question

I was about to add this. I think that there is an improvement in page loads yes, Not very much but it's there.
I'm still trying to find a solution to the server response time (not using a cheap server).

Are you talking about pagespeed insights? What is your response time?
 
Are you using nginx? I'd look into optimizing it along with php-fpm.
I do use Nginx as proxy for Apache. It is supposed to be already optimized out of the box with my control panel but apparently not enough.
Not sure how to optimize this or php-fpm.
 
Are you talking about pagespeed insights? What is your response time?
Yes but not only.
I get 600-700 ms response time. On my old server I used to get less than 350ms.
My new server comes with Nginx, php-fpm, SSD etc... but still it's slower in response time than my old fashion HDD, PHP 5.2 ... I don't get it.
 
I am now getting the following errors all of the sudden, anyone knows what this means?

Code:
ErrorException: Memcache::get(): Server localhost (tcp 11211) failed with: Failed reading line from stream (0) - library/Zend/Cache/Backend/Memcached.php:180


#0 [internal function]: XenForo_Application::handlePhpError(8, 'Memcache::get()...', '/srv/users/club...', 180, Array)
#1 .../forum/library/Zend/Cache/Backend/Memcached.php(180): Memcache->get('xf_data_options')
#2 .../forum/library/Zend/Cache/Core.php(303): Zend_Cache_Backend_Memcached->load('xf_data_options', false)
#3 .../forum/library/XenForo/Model/DataRegistry.php(87): Zend_Cache_Core->load('data_options')
#4 .../forum/library/XenForo/Dependencies/Abstract.php(147): XenForo_Model_DataRegistry->getMulti(Array)
#5 .../forum/library/XenForo/FrontController.php(127): XenForo_Dependencies_Abstract->preLoadData()
#6 .../forum/index.php(13): XenForo_FrontController->run()
#7 {main}


array(3) {
  ["url"] => string(109) "https://www.example.com/forum/threads/clic-animaux-4-chats-porte-bonheur-jusquau-11-d%c3%a9c-au-soir.43692/"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(0) {
  }
 
Memcached connection is timing out.
Thanks, not sure how to run the perl script at all. But from the stats I see that listen_disabled_num is 0 so that shouldn't be the issue.
I really don't know how to "fetch that .pl file".

Are you talking about ping times? Are both servers in the same datacenter?
I'm talking about response time. No they are not in the same datacenter.
But to give you a different indicator it take 3 times longer now for Googlebot to download a page on the average according to webmastertools.
 
What does your memcached config look like?
Just the regular config in fact:
Code:
$config['cache']['backend'] = 'Memcached';
$config['cache']['backendOptions'] = array(
    'compression' => false,
    'servers' => array(
        array(
            // your memcached server IP /address
            'host' => 'localhost',

            // memcached port
            'port' => 11211,
        )
    )
);
 
Just the regular config in fact:
Code:
$config['cache']['backend'] = 'Memcached';
$config['cache']['backendOptions'] = array(
    'compression' => false,
    'servers' => array(
        array(
            // your memcached server IP /address
            'host' => 'localhost',

            // memcached port
            'port' => 11211,
        )
    )
);

/etc/memcached.conf
 
ahhh ok :D.
Here it is:
Code:
# memcached default config file
# 2003 - Jay Bonci <jaybonci@debian.org>
# This configuration file is read by the start-memcached script provided as
# part of the Debian GNU/Linux distribution.

# Run memcached as a daemon. This command is implied, and is not needed for the
# daemon to run. See the README.Debian that comes with this package for more
# information.
-d

# Log memcached's output to /var/log/memcached
logfile /var/log/memcached.log

# Be verbose
# -v

# Be even more verbose (print client commands as well)
# -vv

# Start with a cap of 64 megs of memory. It's reasonable, and the daemon default
# Note that the daemon will grow to this size, but does not start out holding this much
# memory
-m 64

# Default connection port is 11211
-p 11211

# Run the daemon as root. The start-memcached will default to running as root if no
# -u command is present in this config file
-u memcache

# Specify which IP address to listen on. The default is to listen on all IP addresses
# This parameter is one of the only security measures that memcached has, so make sure
# it's listening on a firewalled interface.
-l 127.0.0.1

# Limit the number of simultaneous incoming connections. The daemon default is 1024
# -c 1024

# Lock down all paged memory. Consult with the README and homepage before you do this
# -k

# Return error when memory is exhausted (rather than removing items)
# -M

# Maximize core file limit
# -r
 
Try this,

Code:
# memcached default config file
# 2003 - Jay Bonci <jaybonci@debian.org>
# This configuration file is read by the start-memcached script provided as
# part of the Debian GNU/Linux distribution.

# Run memcached as a daemon. This command is implied, and is not needed for the
# daemon to run. See the README.Debian that comes with this package for more
# information.
-d

# Log memcached's output to /var/log/memcached
logfile /var/log/memcached.log

# Be verbose
# -v

# Be even more verbose (print client commands as well)
# -vv

# Start with a cap of 64 megs of memory. It's reasonable, and the daemon default
# Note that the daemon will grow to this size, but does not start out holding this much
# memory
-m 512

# Default connection port is 11211
-p 11211

# Run the daemon as root. The start-memcached will default to running as root if no
# -u command is present in this config file
-u memcache

# Specify which IP address to listen on. The default is to listen on all IP addresses
# This parameter is one of the only security measures that memcached has, so make sure
# it's listening on a firewalled interface.
-l 127.0.0.1

# Limit the number of simultaneous incoming connections. The daemon default is 1024
-c 1024

# Lock down all paged memory. Consult with the README and homepage before you do this
# -k

# Return error when memory is exhausted (rather than removing items)
# -M

# Maximize core file limit
# -r

and then /etc/init.d/memcached restart or service memcached restart
 
Almost 24h without errors and now it starts again.
I really don't know what the problem is. 4 errors appeared all of the sudden yesterday evening, then for the past 6 hours nothing again...
 
I would start benchmarking my "powerful" server if it really is as powerful as advertised.
 
  • Like
Reactions: Xon
Top Bottom