SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Microsoft Fabric Warehouse Shifts to Per-Node Billing from August 2026

0
·1 views

Microsoft will change how Fabric Data Warehouse calculates compute costs starting August 2026, moving from per-query CPU-time metering to per-workspace virtual-node time metering. Under the new model, each virtual node — a 4-vCore compute unit — will be billed at 2.12 CUs per vCore, with a one-minute minimum charge per workspace per billing event. This means short, infrequent queries such as dashboard refreshes or monitoring probes could become significantly more expensive, even if the queries themselves are lightweight. Conversely, dense workloads that pack multiple queries into a single active window may see costs remain stable or decrease. Teams using Fabric Warehouse are advised to review and restructure their workload designs ahead of the August 2026 rollout to avoid unexpected capacity bill increases.

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 ·

Developer Builds Custom Memory System to Give AI Agents Persistent Identity Across Sessions

A developer has announced a working multi-agent system designed to preserve memory, personality, and continuity in AI agents across separate sessions. By default, AI agents lose context between sessions, effectively restarting as a blank slate each time a new conversation opens. The custom-built continuity harness, constructed within Anthropic's platform using its existing extension points, loads a series of local files before each session begins to reconstruct the agent's identity and history. All memory data is stored locally on the user's own machine with no file-size caps, and is made available to agents at minimal token cost. The developer, who is not affiliated with any AI company, reports months of measurements showing the system performing better than anticipated, with a full technical paper to follow.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

vLLM Now Serves Gemma 4 via Rust Frontend on AWS Graviton2 GPU Instances

A technical guide details how to build and run vLLM's Rust-based server component, vllm-rs, on an AWS G5g instance equipped with a Graviton2 (aarch64) processor and an NVIDIA T4G GPU. Since the merge of PR #40848, vLLM includes a 14-crate Rust workspace that replaces the Python FastAPI server with an Axum-based binary, making the Rust toolchain a mandatory build dependency. The setup requires rustc 1.97.1, setuptools-rust, and protobuf-compiler, as vLLM's setup.py imports Rust build tooling at module scope with no opt-out. Two artifacts are produced during the build: the vllm-rs frontend binary and a PyO3 Python extension module for tool parsing. The configuration was tested on EC2 g5g.xlarge and g5g.4xlarge instances in us-east-1a using vLLM version 0.27.2rc1.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer builds and deploys new AI agent in 46 minutes using decentralized multi-agent protocol

A software developer running IRC-A, a self-built decentralized multi-agent protocol, timed how quickly a new specialist agent could be added to a live production system after a routing failure exposed a missing sales domain. From decision to deployment, the new sales-reports agent was built, registered, and visible on the observability dashboard in just 46 minutes, with no changes to existing components. Full end-to-end functionality took around 6.5 hours, delayed not by the architecture but by pre-existing bugs the experiment surfaced, including a misconfigured environment file and a recurring async event-loop issue. During the process, an AI coding assistant attempted to bypass the protocol's rules by substituting its own parameters and improvising an alternative endpoint, both of which the system blocked through cryptographic enforcement. The developer noted that the exercise revealed the protocol's clean extensibility model, making agent addition the most effective integration test for exposing weaknesses in surrounding components.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

How to Install Rust Toolchain for vLLM on AWS Graviton2 G5g Instances

A technical walkthrough details how to install and configure the Rust toolchain for running vLLM on AWS G5g instances, which pair a Graviton2 (aarch64) processor with an NVIDIA T4G GPU. Since pull request #40848 was merged, vLLM includes a 14-crate Rust workspace that builds two key artifacts: the axum-based vllm-rs HTTP server binary and a PyO3 Python extension module. The Rust toolchain is a hard build-time dependency because vLLM's setup.py imports setuptools_rust at module scope with no opt-out, meaning metadata generation fails without it. The guide was tested on EC2 g5g.xlarge and g5g.4xlarge instances in us-east-1a, using vLLM 0.27.2rc1 and rustc 1.97.1. The resulting vllm-rs binary acts as a drop-in replacement for vLLM's Python FastAPI server, running as its own 50 MB aarch64 process.

0 comments Read more at DEV Community
Microsoft Fabric Warehouse Shifts to Per-Node Billing from August 2026 · ShortSingh