Skip to main content
Introduction
============
collective.catalogcache uses memcached to cache ZCatalog search results.

Caching is transparent. Invalidation code is called at appropriate
places to ensure that the state of the cached results remains consistent.

The use of memcached enables the safe use of caching in a distributed
environment.

*** WARNING ***
collective.catalogcache is a big plaster to put over your site while you
determine why things are slow. Use in production is recommended for the brave /
foolhardy.

Requirements
============
Zope 2.9.6 - Zope 2.10.6. Other versions are possibly supported but not
tested.
memcached. Any recent version should work. Download from
http://www.danga.com/memcached.
python-memcached. Download from
http://pypi.python.org/pypi/python-memcached.

If memcached or python-memcached is not available the catalog will
function as usual.

Installation
============
A buildout is provided at
http://dev.plone.org/collective/browser/collective.catalogcache/trunk/buildout.cfg.
The buildout is for Plone 3, but the product can be used with plain Zope.

To enable collective.catalogcache for an existing installation ensure
that the following is present in your buildout.cfg

In the eggs section collective.catalogcache

In the zcml section collective.catalogcache

You must edit your zope.conf to declare eg.
<environment>
MEMCACHE_SERVERS 127.0.0.1:11211,127.0.0.1:11212
</environment>

You *must* ensure that different logical Zope instances do not use the
same memcache servers. Naturally Zeo clients *must* use the same set of servers.

Run ./bin/buildout -Nv and restart your instance.

Notes on memcached
==================
memcached is designed to run in a distributed environment, hence it is a
good idea to run at least two instances on a single machine. More is possibly
better depending on your hardware.

To start up two memcached instances for use with the example
MEMCACHE_SERVERS declaration do

memcached -u root -d -m 256 -l 0.0.0.0 -p 11211
memcached -u root -d -m 256 -l 0.0.0.0 -p 11212

Changelog
=========

0.2
---

* Better documentation

* Handle infrequent KeyErrors gracefully

0.1
---

* Initial release

Metadata

Release files for collective.catalogcache 0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for collective.catalogcache 0.2
File Size Uploaded Provenance
collective.catalogcache-0.2.tar.gz 11.8 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for collective.catalogcache 0.2
File Interpreter ABI Platform
collective.catalogcache-0.2-py2.4.egg Legacy Egg format - - Details

Total release size: 33.4 kB

Release files / collective.catalogcache-0.2.tar.gz

Download URL collective.catalogcache-0.2.tar.gz
Size 11.8 kB
Tags Source
SHA-256 checksum
How to use checksums
b7259953af3a13b2ed341678c86d6a801b4b0c848afb78ff1c9e975eaf1e1a1b
BLAKE2b-256 checksum
How to use checksums
782354e79b00b61b11ded9d4783b7585f84014d79061355a70f492277a1c4b1f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / collective.catalogcache-0.2-py2.4.egg

Download URL collective.catalogcache-0.2-py2.4.egg
Size 21.5 kB
Tags Egg
SHA-256 checksum
How to use checksums
ecf06d8a5121228218f197e68504bae9576aa9820a2d3eb6c2f6bb8477d49069
BLAKE2b-256 checksum
How to use checksums
e5b77eb9a2d385f04724d3ef6799bf52407e9b7ae300eaee2c246ee3d72c444b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for collective.catalogcache 0.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Release history Release notifications | RSS feed

This release

0.2 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page