ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Reduce latency spikes that appear only when many concurrent future calls are made in Racket 8.6. Background The future library shares a thread pool whose idle threads are evicted after a period specified by the --thread-evict flag (default 60 s). The Racket manual provides no runtime API to query or change this timeout, so the eviction period is fixed f
Observed behavior When an application using the OpenTelemetry SDK with the OTLP exporter handles many concurrent requests, per-span export latency rises sharply compared to sequential traffic. The BatchSpanProcessor is documented to buffer spans and flush them when either maxExportBatchSize is reached or scheduleDelayMillis elapses, but under concurrency it
When using Streamlit’s @st.cache_data decorator, the first request for a given input triggers the underlying function, while subsequent requests reuse the stored result. In a concurrent setting, multiple sessions may attempt to evaluate the same uncached call at the same time. The framework protects against redundant work by serializing access, but it is unc
Goal: Determine whether the increase in broadcast latency observed in Supabase Realtime is caused by connection‑pool exhaustion, PgBouncer backpressure, or Node.js event‑loop lag when many clients open WebSocket connections simultaneously. Constraints: The threshold at which latency becomes noticeable is unknown and may differ between free and paid project t
Packer HTTP Provisioner Concurrency Issue The HTTP provisioner in Packer 1.8+ serves templates via a Go http.Server listening on localhost:55555 by default. When multiple builders are executed in parallel, they share the same listening port, which can create contention for incoming connections. This contention manifests as noticeable latency spikes in the bu
Concurrency Behavior in Async Functions Zig implements async functions as stackless coroutines, but the language does not provide a built-in standard scheduler or runtime. In a concurrent environment where multiple requests are processed via a user-defined event loop, the execution of these coroutines relies on the efficiency of the underlying polling mechan
Goal: Determine whether Helm v3 can reduce latency spikes observed when multiple helm install or helm upgrade commands run concurrently without relying on external serialization. Constraints/uncertainty: The observed latency stems from Kubernetes API server queuing, etcd lock contention, and overlapping exponential backoff retries; it is unclear if adding a
The objective is to assess how the global file lock influences request latency when multiple concurrent requests write to the same database table in Contao. Contao's global lock serializes all file operations, and because no per-request transaction isolation level can be set, concurrent writes may contend for the same table, leading to latency spikes and pos
Portability Gap in Barrier Synchronization Guarantees The Fortran 2018 standard refined OpenMP thread synchronization semantics but left barrier latency as implementation-defined. This creates a compatibility boundary where high-performance codes cannot rely on predictable wait times across GNU gfortran, Intel Fortran, and other compilers. gfortran defaults
racket
opentelemetry
streamlit
supabase
zig
helm
kubernetes
contao