From f6152c6b78ff4cd317ea68250d2e551dc4aa9b53 Mon Sep 17 00:00:00 2001
From: John Chilton <jmchilton@gmail.com>
Date: Wed, 25 Jun 2014 08:01:52 -0500
Subject: [PATCH] Add documentation about local runner destination option
 embed_metadata_in_job.

---
 job_conf.xml.sample_advanced | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/job_conf.xml.sample_advanced b/job_conf.xml.sample_advanced
index ad14177b546..ffbb03cdb8c 100644
--- a/job_conf.xml.sample_advanced
+++ b/job_conf.xml.sample_advanced
@@ -102,6 +102,12 @@
           <!-- Warning: Local slot count doesn't tie up additional worker threads, to prevent over 
                allocating machine define a second local runner with different name and fewer workers
                to run this destination. -->
+          <param id="embed_metadata_in_job">True</param>
+          <!-- Above parameter will be default (with no option to set
+               to False) in an upcoming release of Galaxy, but you can
+               try it early - it will slightly speed up local jobs by
+               embedding metadata calculation in job script itself.
+          -->
           <job_metrics /> 
           <!-- Above element demonstrates embedded job metrics definition - see
                job_metrics_conf.xml.sample for full documentation on possible nested