summaryrefslogtreecommitdiff
path: root/doc/s6-instance-delete.html
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2023-01-09 22:24:26 +0000
committerLaurent Bercot <ska@appnovation.com>2023-01-09 22:24:26 +0000
commitaeb3ad3d8cac8f1f085725711d2d8739b722b61b (patch)
tree2225c0b37c1a19161383c67bdb9043006e8b4fe0 /doc/s6-instance-delete.html
parent724fc63f4736d620173e733a3b35c003a0d82ff8 (diff)
downloads6-aeb3ad3d8cac8f1f085725711d2d8739b722b61b.tar.xz
Next batch of fixes
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'doc/s6-instance-delete.html')
-rw-r--r--doc/s6-instance-delete.html9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/s6-instance-delete.html b/doc/s6-instance-delete.html
index 28eca9c..49530b2 100644
--- a/doc/s6-instance-delete.html
+++ b/doc/s6-instance-delete.html
@@ -66,6 +66,15 @@ on a supervision tree that is specific to the instanced service, and
s6-instance-delete removes a service directory from that tree. </li>
<li> If the template for the service is logged, then s6-instance-delete will
delete both the instance and its logger. </li>
+ <li> s6-instance-delete and <a href="s6-instance-create.html">s6-instance-create</a>
+are relatively expensive operations, because they have to recursively copy or
+delete directories and use the <a href="libs6/ftrigr.html">synchronization mechanism</a>
+with the instance supervisor, compared to
+<a href="s6-instance-control.html">s6-instance-control</a> which only has to send
+commands to already existing supervisors. If you are going to turn instances on and
+off on a regular basis, it is more efficient to keep the instance existing and control
+it with <a href="s6-instance-control.html">s6-instance-control</a> than it is to
+repeatedly create and delete it. </li>
</ul>
</body>