How important is having a database optimized. Doing some "basic" optimizations like clearing the cache, runing the Drupal cron and a couple of things more, your database can change from having 4 GB to just around 200MB... incredible? Not at all, the importance of maintenance tasks :-)
Which tasks? Mainly:
Some interesting links that I have found this week.
After a nice day knowing new people and mainly learning, this is my contribution to the community in this first Drupal Sprint in London:
steps:
download review tools,
1. coder: http://drupal.org/project/coder
2. php code sniffer: http://drupal.org/node/1419988
3. dreditor: http://drupal.org/project/dreditor
4. paraviewsh (automated tool): http://drupal.org/project/pareviewsh
try.github.com
sudo git reset --hard origin/8.x
issue summary template: http://drupal.org/node/1155816
http://core.drupalofficehours.org/
http://drupal.org/project/dreditor --> for chrome/firefox
Novice tags are good for starting to contribute.
Applying a patch in Drupal core:
1. Download the patch,
2. apply: git apply -v [patch]
I am using a solution of vbox (virtual box) and shared folders in our windows work environment (yes, unfortunatelly, but the IT team is in his right to decide which machines we have to use).
My name is Alejandro Moreno Lopez. I'm an spanish developer living in London, degree in Computer Science, who has specialized in PHP and Drupal development.
Debugging cron issues and errors is one of the most tricky things in Drupal. If you are dealing with a big site, with people adding nodes, inserting content which you can't allways force to be commited in the right way, and things like that, it is not unusual to find a cron broken by some "misterious" node.
Well, it is quite easy to find this "misterious" offender, just logging the cron activity. How, very easy, with my new module "cron_killing_finder".
It is published in my "Drupal SandBox": http://drupal.org/sandbox/programadoresweb/1895746