@Test
        @DisplayName("should execute all applicable strategies")
        void shouldExecuteAllApplicableStrategies() throws Exception {
            UpgradeContext context = createMockContext();
            Map<Path, Document> pomMap = Map.of(Paths.get("pom.xml"), mock(Document.class));

            // Mock all strategies as applicable
            for (UpgradeStrategy strategy : mockStrategies) {

### Examples of Replication Tools and Strategies { #examples-of-replication-tools-and-strategies }

There can be several approaches to achieve this, and I'll tell you more about specific strategies in the next chapters, for example when talking about Docker and containers.

import java.util.Arrays;
import java.util.concurrent.atomic.AtomicLongArray;
import org.jspecify.annotations.Nullable;

/**
 * Collections of strategies of generating the k * log(M) bits required for an element to be mapped
 * to a BloomFilter of M bits and k hash functions. These strategies are part of the serialized form
 * of the Bloom filters that use them, thus they must be preserved as is (no updates allowed, only

     * Delegates to StrategyOrchestrator for coordinated strategy execution.
     */
    protected int doUpgrade(UpgradeContext context, String targetModel, Map<Path, Document> pomMap) {
        // Execute strategies using the orchestrator
        try {
            UpgradeResult result = orchestrator.executeStrategies(context, pomMap);

            // Create .mvn directory if needed to avoid root directory warnings

  }

  /**
   * A strategy for adding self-loops to {@linkplain #transitiveClosure(Graph,
   * TransitiveClosureSelfLoopStrategy) the transitive closure graph}. All strategies preserve
   * self-loops that are present in the original graph.
   *
   * <p>The strategies differ based on how they define "cycle incident to a node".
   *
   * @since NEXT
   */
  public enum TransitiveClosureSelfLoopStrategy {
    /**

│   │   ├── SuggestIndexer.java     # Main indexing API
│   │   ├── contents/               # Content parsers and readers
│   │   └── writer/                 # Index writing strategies
│   ├── converter/                  # Text conversion utilities
│   ├── normalizer/                 # Text normalization
│   ├── analysis/                   # Custom analyzers

```

Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using

```bash
helm upgrade -f old_values.yaml my-release minio/minio
```

Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy.

### Configuration

Refer the [Values file](./values.yaml) for all the possible config fields.

當然，同一台機器上除了你的應用之外，通常也會有「其他行程」在執行。

有個有趣的細節是，每個行程的「CPU 使用率」百分比會隨時間大幅「變動」，但「記憶體（RAM）」通常維持相對「穩定」。

如果你的 API 每次做的計算量相近，且客戶很多，那「CPU 使用率」也可能「相對穩定」（而不是快速上下起伏）。

### 複本與擴展的工具與策略範例 { #examples-of-replication-tools-and-strategies }

要達成這些有很多種作法。我會在後續章節（例如談到 Docker 與容器時）介紹更具體的策略。

主要的限制是：必須有「單一」元件負責處理「公開 IP」上的「連接埠」。接著它必須能把通信「轉發」到被複製的「行程／workers」。

以下是一些可能的組合與策略：

- Uvicorn 搭配 `--workers`

        this.bitSize(),
        that.bitSize());
    checkArgument(
        this.strategy.equals(that.strategy),
        "BloomFilters must have equal strategies (%s != %s)",
        this.strategy,
        that.strategy);
    checkArgument(
        this.funnel.equals(that.funnel),
        "BloomFilters must have equal funnels (%s != %s)",
        this.funnel,

3. **Persistent Handle State**: Requires reliable state persistence mechanism
4. **Backward Compatibility**: Must maintain compatibility with SMB2/SMB1

### Mitigation Strategies
1. Implement features behind configuration flags
2. Provide graceful fallback mechanisms
3. Extensive testing with various server configurations
4. Phased rollout with beta testing

## Resource Requirements