Search headlines, summaries and articles to connect the dots.
Amazon SageMaker Inference now supports GPU partitioning with NVIDIA Multi-Instance GPU (MIG), which divides one GPU into hardware-isolated partitions so you can run a different model in each or take a right-sized fraction of a newer accelerator. This post shows how two optional API fields place one model per partition, and what we measured against a whole older GPU.
arXiv:2611.06989v1 Announce Type: new Abstract: Enterprises run business transactions through multi-agent AI systems spanning clouds, large language models (LLMs), orchestration harnesses, and systems of record. Finance receives AI cost only at settlement grain, aggregated by SKU and charge period. The business question (what did this order, claim, or case cost in AI?) cannot be answered from billing data, because providers never see enterprise transaction boundaries. The FinOps Open Cost and Usage Specification (FOCUS) gives billing data one schema across providers but remains settlement-grain even as it adds AI token and requester attribution. We formalize this grain mismatch, derive seven requirements, and propose the Two-Ledger Model: a settlement ledger of FOCUS-conformant billing data joined to an attribution ledger of invocation-grain usage records built on OpenTelemetry GenAI telemetry. A layered correlation spine (trace context, A2A/MCP metadata, business-key correlation, probabilistic matching) assigns each record to its business transaction with recorded method and confidence; a versioned rate card prices usage in near real time; period reconciliation ties both ledgers to the invoice, and the unexplained residual identifies shadow AI. Costs are reported per order, claim, or outcome with agentic cost metrics. A simulation with known ground truth shows the spine sustaining cost coverage above 99% as trace propagation falls to zero, the reconciliation residual recovering planted unmetered spend within 0.24 percentage points while flagging provider billing errors, and mid-flight gating cutting p99 transaction cost by up to 61% at a 2-4% false-pause rate. We propose the attribution ledger as an invocation-grain FOCUS profile for standardization.
# [3.0.0](https://github.com/n8n-io/n8n/compare/n8n@2.45.0...n8n@3.0.0) (2026-10-27) ### Bug Fixes * Add file-type tooltip to artifact download button ([#41490](https://github.com/n8n-io/n8n/issues/41490)) ([4a74f02](https://github.com/n8n-io/n8n/commit/4a74f027e612f31098b354dd3a77b2c2ab98281c)) * **ai-builder:** Check execution:read in Assistant execution reads ([#41863](https://github.com/n8n-io/n8n/issues/41863)) ([a967486](https://github.com/n8n-io/n8n/commit/a9674866d075e989a5ce896432262c9a7dc8b0c7)) * **ai-builder:** Send Assistant model calls through the configured AI transport ([#41948](https://github.com/n8n-io/n8n/issues/41948)) ([9b63561](https://github.com/n8n-io/n8n/commit/9b63561cbb48f06d216f27be3b77722d97e4e74a)) * Allow custom OAuth2 scopes ([#41249](https://github.com/n8n-
# [2.46.0](https://github.com/n8n-io/n8n/compare/n8n@2.45.0...n8n@2.46.0) (2026-10-27) ### Bug Fixes * Add file-type tooltip to artifact download button ([#41490](https://github.com/n8n-io/n8n/issues/41490)) ([4a74f02](https://github.com/n8n-io/n8n/commit/4a74f027e612f31098b354dd3a77b2c2ab98281c)) * **ai-builder:** Check execution:read in Assistant execution reads ([#41863](https://github.com/n8n-io/n8n/issues/41863)) ([a967486](https://github.com/n8n-io/n8n/commit/a9674866d075e989a5ce896432262c9a7dc8b0c7)) * **ai-builder:** Send Assistant model calls through the configured AI transport ([#41948](https://github.com/n8n-io/n8n/issues/41948)) ([9b63561](https://github.com/n8n-io/n8n/commit/9b63561cbb48f06d216f27be3b77722d97e4e74a)) * Allow custom OAuth2 scopes ([#41249](https://github.com/n8
i14 has launched the Laplace 3B model with 3.028 billion parameters, which replaces Softmax attention with Gated Linear Attention (GLA). During inference, its per-sequence recursive state remains constant at 29.5 MB, independent of context length. The model was trained and validated on a single AWS trn2.48xlarge instance (equipped with 16 Trainium 2 chips), achieving a training throughput of 120,000 tokens per second and an inference throughput of 11,544 output tokens per second (with 1,280 concurrent sequences). All performance metrics are based on internal measurements conducted by i14 and the AWS GenAIIC team.
Executable UDFs are now generally available on ClickHouse Cloud across AWS, GCP, and Azure, with native runtimes, network access, observability, and API and Terraform support.
