Adjust properties doc page to fit new format
Properties Reference
====================
-These configuration options may require tuning in specific situations:
+This section describes the most important config properties that
+may be used to tune Presto or alter its behavior when required.
-* ``task.max-worker-threads``:
- Sets the number of threads used by workers to process splits. Increasing this number
- can improve throughput if worker CPU utilization is low and all the threads are in use,
- but will cause increased heap space usage. The number of active threads is available via
- the ``com.facebook.presto.execution.executor.TaskExecutor.RunningSplits`` JMX stat.
+General Properties
+------------------
+
+``distributed-joins-enabled``
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+ * **Type:** ``boolean``
+ * **Default value:** ``true``
-* ``distributed-joins-enabled``:
Use hash distributed joins instead of broadcast joins. Distributed joins
require redistributing both tables using a hash of the join key. This can
be slower (sometimes substantially) than broadcast joins, but allows much
@@ -19,7 +22,32 @@ These configuration options may require tuning in specific situations:
tables on the right side have to fit in distributed memory. This can also be
specified on a per-query basis using the ``distributed_join`` session property.
-* ``node-scheduler.network-topology``:
- Sets the network topology to use when scheduling splits. "legacy" will ignore
- the topology when scheduling splits. "flat" will try to schedule splits on the same
+
+Tasks managment properties
+--------------------------
+
+``task.max-worker-threads``
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+ * **Type:** ``integer``
+ * **Default value:** ``Node CPUs * 2``
+
+ Sets the number of threads used by workers to process splits. Increasing this number
+ can improve throughput if worker CPU utilization is low and all the threads are in use,
+ but will cause increased heap space usage. The number of active threads is available via
+ the ``com.facebook.presto.execution.executor.TaskExecutor.RunningSplits`` JMX stat.
+
+
+Node Scheduler Properties
+-------------------------
+
+``node-scheduler.network-topology``
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+ * **Type:** ``string``
+ * **Allowed values:** ``legacy``, ``flat``
+ * **Default value:** ``legacy``
+
+ Sets the network topology to use when scheduling splits. ``legacy`` will ignore
+ the topology when scheduling splits. ``flat`` will try to schedule splits on the same
host as the data is located by reserving 50% of the work queue for local splits.
