revert: restore original tap configuration The taps were not the cause of the server overload. The problem was the server-side panproto import triggered by git push, which has since been removed in v0.20.7.

9999     image: ghcr.io/bluesky-social/indigo/tap:latest
100100     container_name: cospan-tap
101101     restart: unless-stopped
102-    profiles: ["backfill"]
103-    cpus: 0.25
104102     environment:
105103       TAP_DATABASE_URL: postgres://cospan:${POSTGRES_PASSWORD}@db:5432/tap
106104       TAP_BIND: ":2480"

109107       TAP_RELAY_URL: https://relay1.us-east.bsky.network
110108       TAP_DISABLE_ACKS: "true"
111109       TAP_LOG_LEVEL: info
112-      TAP_RESYNC_PARALLELISM: "1"
113-      TAP_FIREHOSE_PARALLELISM: "2"
110+      TAP_RESYNC_PARALLELISM: "3"
111+      TAP_FIREHOSE_PARALLELISM: "10"
114112     depends_on:
115113       db:
116114         condition: service_healthy

129127     image: ghcr.io/bluesky-social/indigo/tap:latest
130128     container_name: cospan-tap-knots
131129     restart: unless-stopped
132-    profiles: ["backfill"]
133-    cpus: 0.25
134130     environment:
135131       TAP_DATABASE_URL: postgres://cospan:${POSTGRES_PASSWORD}@db:5432/tap_knots
136132       TAP_BIND: ":2480"

139135       TAP_RELAY_URL: https://relay1.us-east.bsky.network
140136       TAP_DISABLE_ACKS: "true"
141137       TAP_LOG_LEVEL: info
142-      TAP_RESYNC_PARALLELISM: "1"
143-      TAP_FIREHOSE_PARALLELISM: "2"
138+      TAP_RESYNC_PARALLELISM: "3"
139+      TAP_FIREHOSE_PARALLELISM: "10"
144140     depends_on:
145141       db:
146142         condition: service_healthy