ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Branching Workflow and Library Divergence Figma Branching allows for isolated design iterations and review cycles before merging changes back into a main file. However, when a file relies on components, styles, or variables from a published Team Library, a divergence can occur between the branch and the main file if the library is updated while the branch re
Goal: Determine the exact concurrency threshold at which TortoiseGit's shared status cache begins to exhibit file‑system lock contention that triggers Windows error 32. Constraints: Working copy larger than 10 000 files, status cache set to the default (shell) mode, real‑time antivirus scanning the .git directory, and simultaneous launch of TortoiseGit conte
We run an HTTP service behind a DigitalOcean Load Balancer forwarding to a small pool of Droplets. Under low traffic, p99 latency is flat. When we ramp concurrent clients, tail latency climbs sharply, and we cannot tell whether the bottleneck is the load balancer tier or the backends. Our understanding of the documented behavior: the load balancer terminates
APNs maintains separate sandbox and production environments with distinct endpoints and token namespaces, and supports both certificate-based per-App ID authentication and token-based authentication using a team key. A design question arises when an app is built for local development versus App Store or production TestFlight distribution. Device tokens are e
The goal is to understand the upper bound of latency between the completion of a Datadog Logs rehydration job and the moment the rehydrated logs become searchable in the platform. Datadog documents that rehydrated logs become searchable after the job finishes, but the exact latency is not guaranteed and can vary with backend load, data volume, and the number
The goal is to lower CPU and memory consumption for a low‑traffic NHibernate‑based web or service application while preventing LazyInitializationException when lazy‑loaded collections are accessed after the session is closed. Constraints include choosing appropriate second‑level cache regions and expiration policies, setting an AdoBatchSize that balances bat
The plan was to get data from aws data exchange, move it to an s3 bucket then query it by aws athena for a data api. Everything works, just feels a bit slow. No matter the dataset nor the query I can't get below 2 second in athena response time. Which is a lot for an API. I checked the best practices but seems that those are also above 2 sec. So my question:
Determine if the 'max-memory' configuration effectively caps heap usage under sustained high-concurrency load in detaspace v2.4.0+. Because the project’s roadmap notes an unresolved decision about enabling asynchronous garbage collection hints by default, it is unclear how this setting interacts with the new memory limit. Does enabling asynchronous garbage c
I would like to filter my kubectl get deploy command based on the value of an annotation. Something similar to kubectl get deploy --annotation stork.libopenstorage.org/skipresource!="true" Currently no clue how to do this and we don't want to add an extra label. Output of both commands above should be something like below: kubectl get deploy NAME READY UP-TO
figma
digitalocean
datadog
nhibernate
detaspace
kubernetes