Commerce Kickstart Scenario
Component type
Categories
Maintenance status
Development status
Component created
Component changed
A set of performance testing scenarios for Commerce Kickstart.
A set of performance testing scenarios for Commerce Kickstart.
This is a module intended for developers that want to use a message broker in combination with drupal. It allows you to send and receive messages without caring about the underlying technical challenges.
Role memory limit is a small module that allow you to set php_memory_limit per role and command line usage(drush).
Lets say your php memory limit is set to 128mb and your site has a lot of blocks and you try to get into block listing page and drupal crashes.
That is becuse there isn't enough memory.
With this module you can set so the admin have more memory, that way you can render pages that needs alot of memory but still keep the original php memory limit for other users.
Run tests against your Drupal instance.
For now, this module includes :
ROADMAP :
You need no longer bother yourself with caching strategies - which view is cached and for how long, how panels are cached. You don't even need to set up boring Rules to clear out those pesky caches. This son of a beast will even purge Varnish for you.
There is a slight problem with the short name having a capital letter A. For the time being you just have to rename it :)
Autocache is cache for kings! It does all the heavy lifting for you. Setup is as easy as:
Switching to Drupal 7.50 makes this module obsolete, the performance issue was fixed in that version of Drupal core.
Module is searching for all modules that were deleted unproperly. Bootstrap optimizer removes this modules from {system} table. It allows Drupal to skip heavy modules/themes directory scan during every page load.
This module is intended to be used as an APC opcode cache flush automator for high performance Drupal-setups.
If you have setup PHP with apc.stat=0 in production and you deploy code updates (with version control or CI or whatever) you need to either restart your webserver or restart php-fpm to flush the opcode cache. You could also execute apc_clear_cache() with a script.