# T5 read-throughput (the measurable half): how many /vector_search ops/s the
# 3-node cluster sustains within SLA, spread round-robin across all 3 pods.
# (T5-as-written's 2.5x WRITE-scaling is structurally impossible on 3-node RF3
# full placement — proven in docs/profiling/m12p4-t5-sharded-throughput.md.)
#
# THIS JOB IS THE Ref-A OWNER-TEST for the re-scoped G-S Scalability guarantee
# (read-throughput) — see docs/planning/milestone-11/guarantee-traceability.md
# (G-S row, re-scoped 2026-06-19). The structural basis (a node serves reads from
# its LOCAL placement, no cross-node forward → per-node capacity adds) is proven by
# the cargo e2e `mp_partial_placement_feed_spans_all_groups` (cluster_cross_shard_reads).
apiVersion: batch/v1
kind: Job
metadata:
  name: tidal-t5-readtput
  namespace: tidaldb-cluster
  labels: { app.kubernetes.io/name: tidal-stress, app.kubernetes.io/part-of: tidaldb }
spec:
  backoffLimit: 0
  ttlSecondsAfterFinished: 7200
  template:
    metadata:
      labels: { app.kubernetes.io/name: tidal-stress, app.kubernetes.io/part-of: tidaldb }
    spec:
      restartPolicy: Never
      automountServiceAccountToken: false
      securityContext: { runAsNonRoot: true, runAsUser: 1000, runAsGroup: 1000, seccompProfile: { type: RuntimeDefault } }
      containers:
        - name: stress
          image: registry.threesix.ai/tidal/stress:m12-rc7-seedretry
          imagePullPolicy: IfNotPresent
          args:
            - --target
            - https://tidaldb-0.tidaldb-peers.tidaldb-cluster.svc.cluster.local:9500
            - --target
            - https://tidaldb-1.tidaldb-peers.tidaldb-cluster.svc.cluster.local:9500
            - --target
            - https://tidaldb-2.tidaldb-peers.tidaldb-cluster.svc.cluster.local:9500
            - --ca-cert
            - /etc/tidaldb/tls/ca.crt
            - --verify-recall
            - --skip-seed
            - --corpus
            - "100000"
            - --embedding-dim
            - "1536"
            - --recall-k
            - "10"
            - --recall-queries
            - "1000"
            - --read-p99-target-ms
            - "10"
            - --recall-target
            - "0.95"
            - --recall-ef-search
            - "64"
            - --ramp
            - "1000:20,2000:20,3000:20,3800:20"
          env:
            - name: TIDAL_API_KEY
              valueFrom: { secretKeyRef: { name: tidaldb-credentials, key: TIDAL_API_KEY } }
            - name: TIDAL_STRESS_LOG
              value: warn
          resources:
            requests: { cpu: "1", memory: 512Mi }
            limits: { cpu: "3", memory: 2Gi }
          securityContext: { allowPrivilegeEscalation: false, readOnlyRootFilesystem: true, capabilities: { drop: ["ALL"] } }
          volumeMounts:
            - { name: cluster-tls, mountPath: /etc/tidaldb/tls, readOnly: true }
      volumes:
        - name: cluster-tls
          secret:
            secretName: tidaldb-cluster-tls
            items: [ { key: ca.crt, path: ca.crt } ]