Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
Topic: redis or memcache(d) |
|
Author |
|
sailor
Joined: 17 Apr 2015 Posts: 82 Location: US
|
Posted: Tue 10 Sep '19 12:20 Post subject: redis or memcache(d) |
|
|
I have Wordpress running and trying to get LiteSpeed cache plugin working. I tried memcache (seems to be quite a bit of confusion or looseness in whether it's memcache or memcached) getting litespeed to use it. But, it doesn't recognize it's there. One of the odd things on the plugin page it states that litespeed doesn't work unless you use their web server. Yet, when you look at a web page, it has their branding on it that it was optimized.
So, I tried redis, but it seems to be a dead on Windows and inforation is very slim. I cannot get it loaded in php 7.3.9 (phpinfo page doesn't show it). I tried various dll versions from https://pecl.php.net/package/redis. I did come across someone stating that igbinary also needed to be enabled, but that didn't help.
Any know what might be wrong? |
|
Back to top |
|
James Blond Moderator
Joined: 19 Jan 2006 Posts: 7373 Location: Germany, Next to Hamburg
|
|
Back to top |
|
sailor
Joined: 17 Apr 2015 Posts: 82 Location: US
|
Posted: Wed 11 Sep '19 19:41 Post subject: |
|
|
Thank you, those settings definitely helped. But I also found another blunder, my php.ini was looking at a prior extension dir version of php.
It seems to be working ok now.
Code: |
extension=igbinary
extension=redis
session.save_handler = redis
session.save_path = "tcp://127.0.0.1:6379"
|
|
|
Back to top |
|
James Blond Moderator
Joined: 19 Jan 2006 Posts: 7373 Location: Germany, Next to Hamburg
|
Posted: Thu 12 Sep '19 11:29 Post subject: |
|
|
make sure that you always have the full path in the extension dir settings
e.g.
Code: |
extension_dir = "C:\php73\ext"
|
|
|
Back to top |
|
alexarun
Joined: 08 Jan 2020 Posts: 1 Location: USA
|
Posted: Wed 08 Jan '20 14:30 Post subject: instagram pva accounts |
|
|
Spam :: Removed |
|
Back to top |
|
knopfler1980
Joined: 31 Mar 2020 Posts: 4 Location: Spain, Madrid
|
Posted: Tue 31 Mar '20 11:58 Post subject: Re: redis or memcache(d) |
|
|
sailor wrote: | (seems to be quite a bit of confusion or looseness in whether it's memcache or memcached) |
Hi.
I had the same worry and I think is replied in stackoverflow, where they say the client is memcache and the "service"(windows)/daemon is memcached: https://stackoverflow.com/questions/1825256/memcache-vs-memcached
Copy from answer author (sorry for the break): Mez
Here is a quick backgrounder in naming conventions (for those unfamiliar), which explains the frustration by the question asker: For many *nix applications, the piece that does the backend work is called a "daemon" (think "service" in Windows-land), while the interface or client application is what you use to control or access the daemon. The daemon is most often named the same as the client, with the letter "d" appended to it. For example "imap" would be a client that connects to the "imapd" daemon.
This naming convention is clearly being adhered to by memcache when you read the introduction to the memcache module (notice the distinction between memcache and memcached in this excerpt):
Memcache module provides handy procedural and object oriented interface to memcached, highly effective caching daemon, which was especially designed to decrease database load in dynamic web applications.
The Memcache module also provides a session handler (memcache).
More information about memcached can be found at » http://www.danga.com/memcached/.
The frustration here is caused by the author of the PHP extension which was badly named memcached, since it shares the same name as the actual daemon called memcached. Notice also that in the introduction to memcached (the php module), it makes mention of libmemcached, which is the shared library (or API) that is used by the module to access the memcached daemon:
memcached is a high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load.
This extension uses libmemcached library to provide API for communicating with memcached servers. It also provides a session handler (memcached).
Information about libmemcached can be found at » http://tangent.org/552/libmemcached.html. |
|
Back to top |
|
|
|
|
|
|