Add server settings for limited memory

Document existing public MLX-LM cache and concurrency options and their synthetic multi-turn checks. No third-party log details are included. Model files and runtime code remain unchanged; full-model capacity is not established by these tests.

TROUBLESHOOTING.md

@@ -43,6 +43,36 @@ separate runtime. GUI integration has not been validated for these full checkpoi
 Do not remove vision/MTP parameters or change the config to force a stock text
 loader to accept the file. All 2,379 saved tensor entries belong to this release.
 
+## Server settings for limited memory
+
+The pinned MLX-LM server retains prompt caches for reuse by default. For a setup
+that favors lower memory use over reuse speed, stop the existing server and start
+it from the same patched Python environment with:
+
+```bash
+mlx_lm.server --model ukisai/Swift-1.5-5bit-MLX \
+  --host 127.0.0.1 --port 8080 \
+  --prompt-cache-size 0 \
+  --prompt-concurrency 1 --decode-concurrency 1 \
+  --prefill-step-size 512
+```
+
+This disables retained prompt caches, limits concurrency to one, and processes
+prefill in smaller chunks. The model weights and their quantization are unchanged.
+The active request still needs its own cache and temporary memory; these options
+do not set a total process-memory cap or guarantee that any context length fits.
+
+Disabling reuse can slow later turns because their history must be processed
+again. It does not remove history that the client includes in the next request.
+Start with a fresh short conversation and increase history while monitoring RAM.
+The model's configured context limit is distinct from the memory needed to run it.
+
+Validation scope: three successive HTTP requests, including a streaming request,
+passed on each small synthetic 4-bit and 5-bit architecture with these settings.
+Retained-cache accounting stayed at zero. These tests did not load the complete
+Swift checkpoint or establish full-model long-context capacity on any Mac.
+No macOS or MLX memory-limit overrides were used in those tests.
+
 ## 3. If a server reports `404 generation thread died`
 
 In the pinned official MLX-LM server, this message means its generation worker
@@ -75,5 +105,5 @@ against a dead worker will not recover it; restart only after addressing the cau
   a tool definition. These are architecture/server checks, not full Swift generation
   or a test of the reported third-party plugin.
 
-The reporter's original traceback is still needed to identify their specific failure.
 These checks do not establish full-model Mac execution or GUI compatibility.
+Diagnosing an individual crash requires its original exception and runtime configuration.

UPLOAD_MANIFEST.json

@@ -38,15 +38,15 @@
     },
     {
       "path": "TROUBLESHOOTING.md",
-      "bytes": 4380,
-      "sha256": "32b67c70616257a0e26e91bbc6b1b880391872f98c4292aece9488940cda9d00",
-      "git_blob_sha1": "2968859f3f32fc644fc20c2fb9e9644e10535e43"
+      "bytes": 5865,
+      "sha256": "d94c7c741398c55b8f9abaa1f1542d7046dc6fab1df7e9ea4b13b59af3945dee",
+      "git_blob_sha1": "3af3c505aff07e4e527e1d2d01b7b8f4cdb5288f"
     },
     {
       "path": "USAGE.md",
-      "bytes": 5431,
-      "sha256": "be75f4abc1868a29866013d9fd6490644f6c06cf3effe6e2704f3e6657affddb",
-      "git_blob_sha1": "db137784896c403a7ee030bb56f335503227baf6"
+      "bytes": 6912,
+      "sha256": "5c401d9f19fdd22c7bdc495bfdc925bc4ef6f9f829827a22918e26e0ba67d0e4",
+      "git_blob_sha1": "8532eaa9e4c661635164a08e3fb00c597191b1a0"
     },
     {
       "path": "chat_template.jinja",
@@ -217,6 +217,6 @@
     }
   ],
   "file_count": 37,
-  "total_bytes": 19310877524,
+  "total_bytes": 19310880490,
   "self_excluded": true
 }

USAGE.md

@@ -102,6 +102,36 @@ The explicit `model.mtp_logits` step and `model.visual` encoder have historical
 component evidence. Integrated image/video chat and speculative generation are
 not implemented; unsupported multimodal generation must not be reported as working.
 
+## Server settings for limited memory
+
+The pinned MLX-LM server retains prompt caches for reuse by default. For a setup
+that favors lower memory use over reuse speed, stop the existing server and start
+it from the same patched Python environment with:
+
+```bash
+mlx_lm.server --model ukisai/Swift-1.5-5bit-MLX \
+  --host 127.0.0.1 --port 8080 \
+  --prompt-cache-size 0 \
+  --prompt-concurrency 1 --decode-concurrency 1 \
+  --prefill-step-size 512
+```
+
+This disables retained prompt caches, limits concurrency to one, and processes
+prefill in smaller chunks. The model weights and their quantization are unchanged.
+The active request still needs its own cache and temporary memory; these options
+do not set a total process-memory cap or guarantee that any context length fits.
+
+Disabling reuse can slow later turns because their history must be processed
+again. It does not remove history that the client includes in the next request.
+Start with a fresh short conversation and increase history while monitoring RAM.
+The model's configured context limit is distinct from the memory needed to run it.
+
+Validation scope: three successive HTTP requests, including a streaming request,
+passed on each small synthetic 4-bit and 5-bit architecture with these settings.
+Retained-cache accounting stayed at zero. These tests did not load the complete
+Swift checkpoint or establish full-model long-context capacity on any Mac.
+No macOS or MLX memory-limit overrides were used in those tests.
+
 ## Conversion provenance
 
 Conversion is not part of installation. If separately authorized, use only the