plone

zope-httpd-4.8.3-1.lbn36.noarch
Service Zope under Apache/mod_wsgi
Located in LBN / … / Plone 5 / BastionLinux 36
zope-httpd-python2-4.8.7-2.lbn36.noarch
Service Zope under Apache/mod_wsgi
Located in LBN / … / Plone and Zope / BastionLinux 36
zope-httpd-python3-4.8.11-1.lbn36.noarch
Service Zope under Apache/mod_wsgi
Located in LBN / … / Plone 5 / BastionLinux 36
zope-httpd-python3-4.8.11-1.lbn36.noarch
Service Zope under Apache/mod_wsgi
Located in LBN / … / Business / BastionLinux 36
zope-instance-2.13.15-3.lbn13.x86_64
Setup of zope unix account and empty Zope database primed for this user
Located in LBN / … / Plone and Zope / BastionLinux 13
zope-jarn.checkinterval-1.0-3.lbn13.noarch
$ checkinterval 1305 The number you see is the recommended check interval for this machine; put it into your zope.conf file: python-check-interval 1305 Now restart Zope and bask in the glow. Why care? The Python Library Reference on the topic of check interval: "This integer value determines how often the interpreter checks for periodic things such as thread switches and signal handlers. The default is 100, meaning the check is performed every 100 Python virtual instructions. Setting it to a larger value may increase performance for programs using threads." Now, the Zope application server is such a program, and it benefits greatly from setting the right check interval. If the value is too low, Zope threads are interrupted unnecessarily, causing a noticable performance hit on today's multi-cpu hardware. Where's the 50 coming from? The constant 50 in the formula was determined by benchmarks performed at Zope Corporation and has become part of the "Zope lore" (See e.g. this post by Matt Kromer). Going beyond pystone/50 produced no further benefits. The value may well be meaningless for applications other than Zope and platforms other than Intel. Background More on check intervals and the GIL from David Beazly. For those back from the Beazly talk: Zope uses long running threads and asyncore, making it (more) independent from OS scheduling issues. Still, the interruption argument holds.
Located in LBN / … / Plone and Zope / BastionLinux 13
zope-jarn.checkinterval-1.0-3.lbn19.noarch
$ checkinterval 1305 The number you see is the recommended check interval for this machine; put it into your zope.conf file: python-check-interval 1305 Now restart Zope and bask in the glow. Why care? The Python Library Reference on the topic of check interval: "This integer value determines how often the interpreter checks for periodic things such as thread switches and signal handlers. The default is 100, meaning the check is performed every 100 Python virtual instructions. Setting it to a larger value may increase performance for programs using threads." Now, the Zope application server is such a program, and it benefits greatly from setting the right check interval. If the value is too low, Zope threads are interrupted unnecessarily, causing a noticable performance hit on today's multi-cpu hardware. Where's the 50 coming from? The constant 50 in the formula was determined by benchmarks performed at Zope Corporation and has become part of the "Zope lore" (See e.g. this post by Matt Kromer). Going beyond pystone/50 produced no further benefits. The value may well be meaningless for applications other than Zope and platforms other than Intel. Background More on check intervals and the GIL from David Beazly. For those back from the Beazly talk: Zope uses long running threads and asyncore, making it (more) independent from OS scheduling issues. Still, the interruption argument holds.
Located in LBN / … / Plone and Zope / BastionLinux 19
zope-jarn.checkinterval-1.0-3.lbn25.noarch
$ checkinterval 1305 The number you see is the recommended check interval for this machine; put it into your zope.conf file: python-check-interval 1305 Now restart Zope and bask in the glow. Why care? The Python Library Reference on the topic of check interval: "This integer value determines how often the interpreter checks for periodic things such as thread switches and signal handlers. The default is 100, meaning the check is performed every 100 Python virtual instructions. Setting it to a larger value may increase performance for programs using threads." Now, the Zope application server is such a program, and it benefits greatly from setting the right check interval. If the value is too low, Zope threads are interrupted unnecessarily, causing a noticable performance hit on today's multi-cpu hardware. Where's the 50 coming from? The constant 50 in the formula was determined by benchmarks performed at Zope Corporation and has become part of the "Zope lore" (See e.g. this post by Matt Kromer). Going beyond pystone/50 produced no further benefits. The value may well be meaningless for applications other than Zope and platforms other than Intel. Background More on check intervals and the GIL from David Beazly. For those back from the Beazly talk: Zope uses long running threads and asyncore, making it (more) independent from OS scheduling issues. Still, the interruption argument holds.
Located in LBN / … / Plone and Zope / BastionLinux 25
zope-Jinja2-2.5.5-3.lbn13.noarch
A small but fast and easy to use stand-alone template engine written in pure python.
Located in LBN / … / Plone and Zope / BastionLinux 13
zope-Jinja2-2.9.5-1.lbn19.noarch
A small but fast and easy to use stand-alone template engine written in pure python.
Located in LBN / … / Plone and Zope / BastionLinux 19

« Previous 10 items Next 10 items » 1 ... 4767 4768 4769 4770 4771 4772 4773 ... 4849

Sections

Search results


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.