SShortSingh.
Back to feed

Three Hidden Budgets That Quietly Kill Web App Performance

0
·88 views

A technical guide published on DEV Community outlines three critical performance constraints that every web application faces: browser bundle size, API rate limits, and database index selectivity. On the frontend, Lighthouse begins penalizing Time to Interactive once gzipped assets exceed 244 kB, and a simple import change — such as switching from full lodash to lodash/get — can reduce payload by up to 8x. API providers like GitHub, OpenAI, and Stripe enforce token-bucket rate limits that allow short bursts but throttle sustained overuse, returning 429 errors when exceeded. On the database side, indexes with low selectivity, such as a status column with only two values, are often ignored by the query planner, forcing full table scans across tens of thousands of rows. The guide provides formulas, threshold references, and a unified PR checklist covering frontend, backend, and database layers, along with four interactive calculators to help developers quantify each budget before merging code.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Thinking Machines releases open-weight Inkling 2 Mini, a 26.4B looped MoE model that runs on 32GB Macs

Thinking Machines Lab has released Inkling 2 Mini, an open-weight language model with 26.4 billion parameters, under the Apache 2.0 license on Hugging Face. The model uses a Looped Transformer design that reuses its middle layers, delivering the computation of 48 layer applications from 24 stored layers. Its checkpoint is about 20GB, allowing it to run on a Mac with 32GB unified memory or a single GPU such as the NVIDIA DGX Spark. The model combines this looping with a sparse Mixture-of-Experts feed-forward network of 128 experts, activating 8 per token. It accepts text and image inputs and produces text outputs, and it follows the larger 594-billion-parameter Inkling 2 Small released in November.

0
ProgrammingDEV Community ·

cmdbook Pro Adds Shells That Open Inside a Running Command's Folder With Its Variables

A developer describes the hassle of opening new terminal tabs to query a running API, which start in the wrong folder and lack the needed environment variables. The article introduces cmdbook's Integrated Terminal, which opens a shell directly from a running command's run panel. That shell starts in the command's working directory and inherits its variables, presets, and secrets, which can be disabled in Settings. Users can open several shells per run, and they close automatically when the panel is closed. The feature is positioned as a complement to, not a replacement for, the user's regular terminal, and it is part of cmdbook Pro.

0
ProgrammingDEV Community ·

OpenRouter Prices for One Open-Weight Model Vary 16x Across Providers

A daily price index found that a single open-weight model on the OpenRouter marketplace spanned a 16.08x gap in blended per-token prices. The model, deepseek-v4.1-flash-1017, had 50 endpoints from 41 providers, with prices ranging from $0.12 to $1.95 per 1M tokens. The cheapest endpoint, from provider Ambient, used fp4 quantization, a lower-precision format than the fp8 most common among endpoints that reported their precision. Nineteen of the 50 endpoints reported no precision at all, which complicates direct comparison. The authors argue that quoting a single per-model price hides this spread and recommend reporting precision alongside any price figure.

0
ProgrammingDEV Community ·

Redacted PDFs Can Often Be Recovered: Tests of Four Redaction Methods

A test of four common redaction approaches found that many PDFs can be unredacted in seconds, depending on how the redaction was applied. Black rectangles drawn over text and comment-style annotations both left the covered words extractable by copy and paste. Only a true redaction saved as a new file, or a page flattened into an image, removed the hidden text. The test file also showed that the same personal details often appear in other places, such as a second page, document properties, or bookmarks, and those remained even after the covered text was removed. The author recommends checking every part of a file before sharing it.