Introduction
experimental.opaquespeedup is an approach to speed up event handling in Plone 3. Currently all events on content objects are getting dispatched to so called “opaque” objects, which are sub-objects not handled by OFS’s ObjectManager class. Apart from the commenting framework such objects are mostly unused nowadays. However, for dispatching every single fired events CMFCatalogAware’s rather expensive method opaqueItems is used in order to collect all “opaque” objects for a given folderish object. The method call wakes up all objects in the folder and is completely uncached. So the more objects reside in a folder and the more event subscribers are being used by the system, the slower things get. And all events count.
This package tries to optimize things by replacing opaqueItems with a version that’ll query the catalog for contained “opaque” objects and cache the results. Initial tests indicate a significant performance improvement.
Changelog
1.0 - 2009-05-22
Package metadata cleanup. [hannosch]
1.0a1 - 2008-09-02
Initial release [tesdal, witsch]
Release files for experimental.opaquespeedup 1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| experimental.opaquespeedup-1.0.zip | 13.5 kB | Without provenance | Details for experimental.opaquespeedup-1.0.zip |
Release files / experimental.opaquespeedup-1.0.zip
| Download URL | experimental.opaquespeedup-1.0.zip |
|---|---|
| Size | 13.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0eb8106b2ed28d5fa244428a26bd9a6a747d732ab817a4ec9dc8411b06fb0321
|
|
BLAKE2b-256 checksum How to use checksums |
71c3dc4758bb187b87183fb8b1883c54491d022f4c591c1d751f1a5106d33683
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for experimental.opaquespeedup 1.0
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
