Async/await in ASP.NET Core: improves scalability more than raw speed

·1 views

A senior .NET developer explains that adding async and await does not automatically make an ASP.NET Core API faster. The main benefit is more efficient use of threads, especially for I/O-bound work such as database queries, external HTTP calls and file access. Asynchronous methods release their thread while waiting for an I/O operation, allowing it to serve other requests in the meantime. The article notes that a database query taking 200 ms will not become 100 ms just because it is async, since database performance factors still apply. The advantage becomes most visible under high concurrency, where the application can handle more simultaneous requests before thread pool pressure becomes a bottleneck.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Apple unveils new 14-inch MacBook Pro powered by M6 chip

Apple has announced a new 14-inch MacBook Pro equipped with its M6 processor. The announcement was published on the company's official newsroom. The source material provided is limited to a link and community discussion metrics, so specific performance, pricing, and availability details are not confirmed here. Readers are encouraged to consult Apple's newsroom post for full specifications.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

ShellGhost: A Local Open-Weight Assistant That Lives in Your Terminal

A developer has published a project called ShellGhost, a local open-weight AI tool designed to run inside a terminal. The announcement appeared on DEV Community under the original headline describing it as a spirit that haunts the author's shell. The source article's body text did not render properly, so details about its features, architecture, and performance could not be confirmed. The project is presented as a personal experiment rather than a commercial product. Further specifics would require reading the original post directly.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Local LLMs vs Cloud APIs: VRAM Limits, Cost Break-Even, and Routing Design

Engineers are advised against relying exclusively on either on-premises hardware or hosted provider APIs, and should instead decide which workloads suit each. The choice depends on three factors: available GPU memory, the token volume at which costs break even, and data isolation requirements. Model weights must fit in memory, and quantization can cut memory needs roughly fourfold, while mixture-of-experts designs reduce per-token compute. Based on the article's estimates, a roughly $2,500 workstation costs about $83 monthly, and pays off against frontier cloud pricing at around 8 million tokens per month. Local deployment offers physical data isolation, whereas hosted APIs rely on contractual safeguards, and on-premises setups must manage growing KV cache demands for long contexts.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Confirm Two Independent CLI Runs Match Before Freezing a Transcript Baseline

A DEV Community article argues that a repository's behavior should only be frozen as a golden baseline once two independent runs yield identical transcripts, since disagreement means there is no reliable baseline. It recommends testing at the process boundary, capturing exit codes, stdout, stderr, and a SHA-256 digest of the output file tree rather than function return values. The author describes using fixture directories, isolated temp copies, and a short, explicitly documented set of regex normalizers for nondeterministic fields like UUIDs and timestamps. To expose ordering nondeterminism, the process runs twice under different PYTHONHASHSEED values, and any divergence is fixed by sorting the data rather than pinning the seed. The article includes a roughly sixty-line dependency-free Python harness for recording and checking these golden files.

0 comments Read more at DEV Community