Performance

This module integrates development with Meteor (http://meteor.com/) and Drupal. Meteor is a platform built on Node.JS.

The module implements the lightweight lazy load plugin called unveil.js

Lets cron clean all cache tables.

Why Mongo Node?

This module is supposed to be a performance boost replacement for the standard Node in Drupal!

Advantages over node:

• performance: faster saving and loading
• no tables for entity types or bundles in MySQL (too many tables already)
• creation of new entity types and entity bundles (node only lets you create bundles)
• similar content administration to the node (no coding required as you have to in custom entities)

No base table:

The base entity is without a base table, all the properties and fields attached
to the Mongo entities are stored directly in Mongo.
This leads to faster saving and loading of entities, and less tables in Drupal.

No automatic revisions for every node created

At this moment mongo nodes revisions are not supported.
For use cases where revisions are not needed the module is better than the
standard node because it doesn't save a revision for every item.

Create new entity types and bundles

You can create new entity types with multiple entity bundles via interface or
code configuration also. You don't need a new module for every new entity.

Requirements

• Entity Api
• MongoDB

Installation

Turbolinks makes following links in your web application faster.

This module is a drop-in replacement for Drupal's database logging module (dblog), providing performance enhancements and finer-grained configuration.

Features

• Provides all of the functionality which dblog provides.
• Allows you to configure which message severities are logged.
• Allows configuration based on user type (anonymous, authenticated and cron).
• Lets you enable or disable special treatment for 403 and 404 pages, if you need reporting.
• Can buffer log message, so that only one database write is needed per page request regardless of the number of log messages (configurable).

Usage

1. Enable this module and disable Drupal's database logging module.
2. Visit the 'Logging and errors' page on your site (admin/config/development/logging).
3. Configure the additional options you require, or leave as default.

Possible extensions

Use queuing instead of a shutdown function to write buffered log entries, so that alternative queue backends can be used, such as mongoDB. This would mean that logging would not require per-page database writes, but log entries would be delayed until next cron run.

Similar projects