cache

Hi all, (first of all, sorry for my english)

I'm start using Drupal and this is my setup:

Gentoo Linux 64bit with:

nginx
Fastcgi PHP-FPM
PHP 5.3
MySQL Server 5.1
xCache Opcode cache
Drupal 7.9 with heavy / large modules ... (views, panels, display suite, entity API ... etc) using the InnoDB engine.

Quad-core Intel CPU
3x2GB (6GB) DDR3 RAM
500GB 7200rpm SATA HD

In this machine, plus the installation of Drupal, there are also a OpenX Ad Server 2.8 (myisam engine & memcached).

Buenas,
en la empresa tenemos una instancia de Amazon de las grandes y nos lleva el sitio sobrada.
El problema es que lanzamos boletines y a lo largo de la semana solemos tener un par de día con un pico bastante fuerte. Para solventarlo hemos decidido, como primera medida de choque, poner Varnish.
El caso es que lo monté y lo configuré, pero, pese a que el servidor ahora responde mucho mejor a los picos, creo que me cachea poco, me gustaría que cacheara un poco mas para quitarle aun mayor parte al Apache.

Our site (http://en.commtap.org), uses a fair amount of JavaScript to modify how its pages are presented according to a visitor's preferences. Unfortunately it appears that a significant number of our visitors don't have JavaScript enabled in their browsers - and do not have the means to enable it - these computers are in primary schools. In this case, the alternative would be for a visitor's preferences to be processed server side when the page is being created in Drupal. This would mean that we would have to turn page caching off, slowing down the delivery of pages for everyone.

Recurro a los experimentados con Drupal porque no encuentro esta info en la web...

Tengo un bloque que tiene en la opciones de visibilidad código PHP que hace que solo muestre el bloque cuando me visitan desde el exterior.

En el site tengo cache de página y cache de bloques habilitado.

Hoy veo que el bloque es visible para mi aunque no debiese. El código estoy seguro que es correcto...

Significa que el modo cache hace que el código puesto en la opciones de visibilidad del bloque se ignore una vez que la cache ya fue creada?

Thanks for the linode VPS tutorial on how to install mercury, I'm pretty sure I'd be flailing about biting my toenails had I not found it. But before I go ahead and install and configure it, I can't seem to figure out whether mercury is what I'd be needing because most of my users will be authenticated users.

From what it sounds like, varnish+pressflow+awesomesauce=Mercury and that is best for boatloads of anonymous users. So my question is what kind of performance gain would I get if I install mercury running a site built for authenticated users?

Holas,

Tengo un problema con Views.

Tengo un View creado con su Display respectivo, en el display tengo Path: jobs, e incluso pedi que estuviera en el Navigation menu. Sin embargo ninguna de las dos cosas funciona:
/jobs = page not found
Y el item no se agrego al menu Navigation.

Alguien en el foro me dijo q limpiara el cache pero quisiera saber por que hacer eso, y si fuera necesario q tipo de cambios requiren limpiar el cache para evitar estos problemas.

Gracias

Comparação de várias backends e módulos de cache no Drupal.
Inclui um odt e pdf anexados.

Benchmarking tests for a heavy drupal 6 demo site

Characteristics:

• Linode VPS, 1GB RAM, single server setup
• Debian GNU/Linux 5.0 64-bit
• Kernel 2.6.35.4-x86_64-linode16, x86_64
• Apache 2.2.9
• PHP 5.2.6, running as FastCGI
• APC 3.0.19
• Memcached 1.2.2
• MySQL 5.0.51
• Drupal 6.20
• Authenticated User Page Caching (authcache) 1.0-rc2
• Cache Router (cachrouter) 1.0-rc1
• Cache Router Statistics (cacherouter_stats) 1.0-beta3
• Memcache API and Integration (memcache) 1.0-beta3
• JavaScript Aggregator (javascript_aggregator) 1.5
• CSS Gzip (css_gzip) 1.3
• heavy drupal site (182 modules, 95 projects)

Já sabem do módulo Cache Backport?

É um backport da cache.inc do Drupal 7 directamente para o Drupal 6, capaz de funcionar com as Cache backends do Drupal 7, sem nenhuma ou com poucas modificações.

these Cache APIs/backends work fully with Cache Backport:
- File Cache (D7, no patch required) - sucessor to fastpath_fscache and Cache Router
- APC - Alternative PHP Cache (D7, no patch required) - sucessor to Cache Router
- Memcache API and Integration (D7, patch required)
- Database / DBTNG (from D7, supplied with Cache Backport)

Last week a new module appeared on Drupal.org named Purge.
Purge is designed to selectively purge affected pages from a caching reverse proxy after changes are made to the site. The Purge module can be used to add this functionality to the nginx native cache.

We are building a website where anonymous users need to be validated using their IP address and hence providing them with different content and page builds based on their identity detected by their current IP. We have full control of the IP allocation and are able to determine users based on that. We wish that users do not need to register an account with the website to access this content. Boost is being used for caching.