AllyshipContent Radar

News 2905

Chủ đề cộng đồng đang thảo luận

Crawl live-1795130100000 · 06:15 20 thg 11, 2026 · Xuất bản 06:31 20 thg 11, 2026

96 / 2905 chủ đề đạt ngưỡng 55 trong khoảng này.

1

Gemini 4 Neon is getting rave reviews, so I made a new video comparing it to Opus 5.5, my favorite model for everyday work.

56

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

petergyang 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Gemini 4 Neon is getting rave reviews, so I made a new video comparing it to Opus 5.5, my favorite model for everyday work. Some takeaways: 1. Opus is still better at 3D and design from my testing, but Neon is on par or better at writing and personality, which is a huge accomplishment. 2. @Google Gemini 4 has 3 models, but in reality I think I'll use Neon for 99% of tasks. It's much faster than Carbon and its results are just as good. 3. The $100/mo Gemini Ultra subscription is a steal. You get Gemini 4, YouTube Premium Family (my favorite subscription ever) for ad-free YouTube and Music, 20 TB of storage for all your photos and files, and more. 📌 Watch me test Neon vs Opus across 5 use cases here: https://youtu.be/iYIWuI5WfUo

3

@badlogicgames his approach is amazing. it's in fact so amazing that i made an entire framework around that approach a year ago

56

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

devagrawal09 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

@badlogicgames his approach is amazing. it's in fact so amazing that i made an entire framework around that approach a year ago https://devagrawal09.github.io/specter/

4

Join us next Tuesday, November 24 in San Francisco for an evening with the teams building open weight models

56

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Join us next Tuesday, November 24 in San Francisco for an evening with the teams building open weight models We'll kick things off with the latest Artificial Analysis benchmark data, followed by lightning talks and a panel. Register 👇 https://luma.com/artifi-mkho?utm_source=x

5

Amazon SageMaker AI now detects latency drift, idle GPUs, and missed optimizations on your inference endpoints

56

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Hazim Qudah 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p>Every inference endpoint is well tuned the day it goes into production. Teams choose an instance type, serving configuration, and scaling settings that suit the model and its traffic at launch. With the endpoint serving smoothly, they understandably move on to the next priority. The workload, however, rarely stays still. Traffic patterns evolve, prompts grow longer, serving engines such as vLLM ship new releases, SageMaker inference develops new optimization techniques, and new fine-tuned checkpoints change the resources your model needs. Over time, a well-tuned endpoint quietly drifts. Latency and time to first token edge upward. A configuration that was never quite ideal keeps missing available performance gains. A GPU provisioned for demand that never materialized sits idle week after week. Because nothing has failed, no alarm sounds, and the drift goes unnoticed until users feel it or the bill reflects it.</p> <p><a href="https://aws.amazon.com/sagemaker/ai/" target="_blank" rel="noopener">Amazon SageMaker AI</a> now monitors your generative AI inference endpoints and tells you when a change could improve performance or lower cost by using <a href="https://aws.amazon.com/blogs/machine-learning/amazon-sagemaker-ai-now-supports-optimized-generative-ai-inference-recommendations/" target="_blank" rel="noopener">Generative AI optimized inference recommendations</a>&nbsp;feature with Agentic experience in &nbsp;<a href="https://aws.amazon.com/sagemaker/ai/studio/" target="_blank" rel="noopener">Amazon SageMaker Studio</a>. Monitoring is on by default for SageMaker AI inference endpoints using vLLM serving containers and GPU instances, with no setup required, and you can opt out of endpoints. SageMaker AI looks only at operational signals: latency, GPU utilization, and the endpoint’s serving configuration. It does not read your requests or responses. From those signals, it surfaces three kinds of findings:</p> <ul> <li><strong>Latency drift:</strong> A week-over-week rise in median (p50) end-to-end latency or time to first token.</li> <li><strong>Unused capacity:</strong> GPUs you pay for that sit mostly idle.</li> <li><strong>Configuration gaps:</strong> A serving container that’s missing newer performance improvements or security patches, or an optimization such as speculative decoding or GPU kernel tuning that your model supports but the endpoint doesn’t use.</li> </ul> <p>SageMaker AI sends a finding through AWS Health, with one notification per endpoint that covers that endpoint’s findings. When a notification arrives, you can act on it in one place. It opens the SageMaker AI agentic experience in Amazon SageMaker Studio with the endpoint, and its recent traffic already filled in. From there, you run inference recommendations to benchmark your current configuration against alternatives and compare them side by side on response time, throughput, and cost per million tokens. That turns a judgment call into a decision backed by data. Benchmarks run on separate compute, and nothing changes on your endpoint until you choose to apply a result.</p> <p>In this post, we show how SageMaker AI monitors your endpoints and how to read the notifications it sends through AWS Health. We then show how to go from a notification to a benchmarked decision in SageMaker Studio. We walk through three example scenarios, show how to apply or dismiss a recommendation safely, and explain how to opt an endpoint out of monitoring.</p> <h2 id="solution-overview">Solution overview</h2> <p>SageMaker AI inference recommendations follow a four-step loop: observe, notify, recommend, and decide. Each step is designed so that you stay in control, and your production endpoint isn’t changed without your explicit action.</p> <ol type="1"> <li><strong>Observe –</strong> Monitoring of latency and capacity usage is on by default for eligible endpoints. It doesn’t read your requests or responses, and it carries no additional GPU cost.</li> <li><strong>Notify –</strong>&nbsp;When there is something worth acting on, you receive a plain language notification in AWS Health, plus email, explaining what was observed, why it matters, and a recommended next step.</li> <li><strong>Recommend (opt in) –</strong>&nbsp;One selection opens the SageMaker AI agentic experience in SageMaker Studio, prefilled with the endpoint and its observed traffic, so you can benchmark alternatives on separate compute.</li> <li><strong>Decide –</strong>&nbsp;Compare response time, throughput, and cost side by side. Production is not changed until you apply a result.</li> </ol> <p>The feature produces a few types of findings. The following table summarizes what triggers each one and what gets tested when you choose to benchmark.</p> <table border="1px" width="100%" cellpadding="10px"> <tbody> <tr> <td><strong>Finding</strong></td> <td><strong>What triggers it</strong></td> <td><strong>What a benchmark tests</strong></td> </tr> <tr> <td>Latency drift</td> <td>Response time moves relative to the endpoint’s week-over-week trends</td> <td>Tensor parallelism settings and alternate instance types or sizes</td> </tr> <tr> <td>Underutilized GPUs</td> <td>GPU utilization stays well below capacity over the window</td> <td>Cheaper instance types and smaller sizes at observed peak traffic</td> </tr> <tr> <td>Speculative decoding not enabled</td> <td>Model and container support it, but it is off (configuration based)</td> <td>Current configuration compared to speculative decoding enabled</td> </tr> <tr> <td>Serving container</td> <td>The endpoint’s serving container has a newer version with a performance improvement and security patches for critical and high finding Common Vulnerabilities and Exposures (CVEs).</td> <td>Current compared to updated container</td> </tr> <tr> <td>Untuned GPU kernels</td> <td>Kernel configuration is not tuned for the model and hardware</td> <td>Default compared to tuned kernels</td> </tr> </tbody> </table> <h2 id="prerequisites">Prerequisite

6

check out the results:

56

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

hesamation 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

check out the results: https://crusbench.com

7

Inside Amazon Connect Talent: The science of structured AI interviews

56

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Sunitha Srivatsa 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p><span class="TextRun SCXW252313659 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW252313659 BCX0">For organizations hiring </span><span class="NormalTextRun SCXW252313659 BCX0">hundreds or </span><span class="NormalTextRun SCXW252313659 BCX0">thousands of people, every interview presents the same challenge: How do you give candidates a consistent opportunity to </span><span class="NormalTextRun SCXW252313659 BCX0">demonstrate</span><span class="NormalTextRun SCXW252313659 BCX0"> their skills while gathering the evidence needed to make informed hiring decisions?</span></span><span class="EOP Selected SCXW252313659 BCX0" data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:278}">&nbsp;</span></p> <p><span class="TextRun SCXW193008649 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW193008649 BCX0">Structured behavioral interviews offer a research-backed approach to this challenge. They use consistent, job-related questions and clear scoring criteria to give candidates an opportunity to </span><span class="NormalTextRun SCXW193008649 BCX0">demonstrate</span><span class="NormalTextRun SCXW193008649 BCX0"> their skills. Decades of research in industrial-organizational (I-O) psychology have shown that structured interviews help organizations evaluate candidates and predict job performance (Schmidt &amp; Hunter, 1998; Sackett et al., 2022). Yet delivering </span><span class="NormalTextRun SCXW193008649 BCX0">structured interviews</span><span class="NormalTextRun SCXW193008649 BCX0"> at scale requires </span><span class="NormalTextRun SCXW193008649 BCX0">significant time</span><span class="NormalTextRun SCXW193008649 BCX0"> and </span><span class="NormalTextRun SCXW193008649 BCX0">expertise</span><span class="NormalTextRun SCXW193008649 BCX0"> to develop</span><span class="NormalTextRun SCXW193008649 BCX0"> competencies, </span><span class="NormalTextRun SCXW193008649 BCX0">create q</span><span class="NormalTextRun SCXW193008649 BCX0">uestions, train interviewers, and evaluate responses consistently</span><span class="NormalTextRun SCXW193008649 BCX0">.</span></span><span class="EOP Selected SCXW193008649 BCX0" data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:278}">&nbsp;</span></p> <p><span data-contrast="auto"><a href="https://aws.amazon.com/products/connect/talent/" target="_blank" rel="noopener">Amazon Connect Talent</a> <span class="NormalTextRun SCXW175523192 BCX0">brings established hiring science to AI-led interviews at scale. </span><span class="NormalTextRun SCXW175523192 BCX0">Connect Talent </span><span class="NormalTextRun SCXW175523192 BCX0">uses structured questions, adaptive follow-ups, and evidence-based scoring to help organizations gather consistent, job-related information while giving more candidates the opportunity to demonstrate their strengths.</span></span></p> <p><span class="TextRun SCXW66502508 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW66502508 BCX0">We built Connect Talent around three core design principles and evaluated how well the service </span><span class="NormalTextRun ContextualSpellingAndGrammarErrorV2Themed SCXW66502508 BCX0">applies</span><span class="NormalTextRun SCXW66502508 BCX0"> them through </span><span class="NormalTextRun SCXW66502508 BCX0">a combination of </span><span class="NormalTextRun SCXW66502508 BCX0">internal research and independent expert review. </span><span class="NormalTextRun SCXW66502508 BCX0">The </span><span class="NormalTextRun SCXW66502508 BCX0">findings offer a closer look at the science behind </span><span class="NormalTextRun SCXW66502508 BCX0">Connect Talent’s </span><span class="NormalTextRun SCXW66502508 BCX0">AI-le</span><span class="NormalTextRun SCXW66502508 BCX0">d,</span><span class="NormalTextRun SCXW66502508 BCX0"> structured interviewing.</span></span><span class="EOP Selected SCXW66502508 BCX0" data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:278}">&nbsp;</span></p> <h2><b><span data-contrast="auto">Three core design principles</span></b></h2> <h3><b><span data-contrast="auto">1. Build interviews around job-related evidence</span></b></h3> <p><span class="TextRun SCXW227730746 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW227730746 BCX0">Connect Talent builds each interview around the competencies </span><span class="NormalTextRun SCXW227730746 BCX0">required</span><span class="NormalTextRun SCXW227730746 BCX0"> for the role. The service uses job requirements and </span><span class="NormalTextRun ContextualSpellingAndGrammarErrorV2Themed SCXW227730746 BCX0">established</span><span class="NormalTextRun SCXW227730746 BCX0"> occupational frameworks to create behaviorally anchored scorecards. Each scorecard defines specific strength and concern signals, and every interview question targets the behaviors it aims to uncover.</span></span><span class="EOP Selected SCXW227730746 BCX0" data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:278}">&nbsp;</span></p> <p><span class="TextRun SCXW128739577 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW128739577 BCX0">The AI interviewer also adapts to each response. After every answer, it checks whether the candidate has provided enough evidence for the competency being assessed. When details are missing, it asks targeted follow-up questions. This approach preserves the structure of the interview while giving candidates more opportunities to explain their experience.</span></span><span class="EOP Selected SCXW128739577 BCX0" data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:278}">&nbsp;</span></p> <h3><b><span data-contrast="auto">2. Separate interviewing from scoring</span></b></h3> <p><span c

8

Genie 4 is the first model we launched on the new Live Interactions API, bringing native WebRTC (with ephemeral tokens) and WebSocket support directly to Interactions and Gemini API.

56

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

_philschmid 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Genie 4 is the first model we launched on the new Live Interactions API, bringing native WebRTC (with ephemeral tokens) and WebSocket support directly to Interactions and Gemini API. This is part of our ongoing work to improve Gemini API experience. When we started building the Interactions API, one of our main goals was making sure standard API calls and real-time and long running sessions share one consistent interface. We put a lot of effort into getting the primitives right, and we have big plans. I would love your feedback as we build this out: what do you want to see as we bring protocols like WebSockets and WebRTC to more Gemini models? What is still missing for building better agent experiences or real-time apps? In the meantime, you can try Genie 4 in the docs: https://aistudio.google.com/docs/genie Media

9

Playing GTA & not following the Anthropic IPO? Following the IPO & not playing GTA?

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Ethan Mollick 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Playing GTA & not following the Anthropic IPO? Following the IPO & not playing GTA? Why not both? I had Fable make a thing where you steal cars & go on missions in a world where everything from your wanted level to weather is driven by ANT's stock price https://market-order-city.netlify.app/ Media

10

Watch → https://goo.gle/4AIPYYS

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Google DeepMind 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Watch → https://goo.gle/4AIPYYS Spotify → https://goo.gle/4iSB5x5 Apple Podcasts → https://goo.gle/4iSrk21 Or listen wherever you get your podcasts! 🎧

11

Our SVP @koraykv believes there won't be a single test or benchmark that tells us we've reached AGI. Instead, progress looks like models becoming less spiky and more reliable across our daily lives.

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Google DeepMind 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Our SVP @koraykv believes there won't be a single test or benchmark that tells us we've reached AGI. Instead, progress looks like models becoming less spiky and more reliable across our daily lives. Listen in as he and @fryrsquared discuss the road ahead ↓ Timecodes: 00:00 Introduction 01:26 Evolution of Google DeepMind 04:41 Products as a path to AGI 13:01 Architectures and models 24:40 Recursive self improvement 30:50 Safety and agent teams 40:35 Benchmarks Media

12

Introducing Higgsfield GPU Harness.

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

higgsfield 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Introducing Higgsfield GPU Harness. Rent on-demand GPUs in Claude and ChatGPT to render, run open-weight models and train LoRAs. Let several AI agents work on your professional apps in the cloud at once, from any device. Black Friday deal, live now: get GPUs at up to 64% OFF. Media

13

How much do you automate your life? (2)

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

luongnv89 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

How much do you automate your life? (2) This is how i consume articles and blog posts nowadays - send the link to my bot on Telegram, it become a core subject of a new podcast episode - a bot goes looking for other sources: some explain the ideas more simply, some bring data, some disagree =>full picture, not just one opinion - a bot writes a 2-host podcast (Bob and Alice, heygen voice, free from @OpenRouter, thank to @HeyGen ) checks every fact against its source, and explains the hard parts with simple metaphors - the episode goes live on http://luongnv.com/podcast - if one topic really catches me and I want to dig deeper: one command sends the original article to my reMarkable as a clean PDF, so I can read it slowly and take notes with a pen (the skill is open source: http://github.com/luongnv89/remarkable-skills) I send a link, I get a podcast. Everything else is automatic Here is the latest one on verification from @addyosmani , super interesting https://luongnv.com/podcast/episodes/2026-11-19_how-the-claude-code-team-thinks-about/

14

QDA: Closed-Loop LLM Quantization Design with Agents

86

5 tiếng nói · chưa gắn nhãn trưởng lab · 2 nền tảng · 9 tương tác đã đo · Nguồn crawl

Xingyang Li, Tianlang Zhao và 3 nguồn khác 1 bài viết · Hugging Face Papers, X
Biên tập tiếng Việt
Chi tiết nguồn

Bài báo nêu rằng post-training quantization là cách tiêu chuẩn để phục vụ LLM với chi phí thấp, nhưng công thức quantization tốt phụ thuộc vào từng mô hình và độ chính xác, nên chuyên gia phải thiết kế lại cho mỗi mô hình. Họ giới thiệu QDA, nơi một agent thiết kế recipe cho từng mô hình và độ chính xác. QDA đánh giá nhanh bằng cách chấm candidate theo KL divergence đầu ra so với mô hình gốc trên reasoning traces mà agent không thấy, và kiểm tra thêm các candidate hứa hẹn bằng long generations để bắt lỗi như repetition loops.

Post-training quantization is the standard way to serve large language models at low cost. However, the best quantization recipe differs across models and precisions. As a result, experts must redesign it for every new model, which is time-consuming and often sub-optimal. Fortunately, an LLM agent can take over this design by refining the recipe over rounds of building and evaluating candidates, so that more rounds lead to better recipes. However, evaluating one quantized reasoning model takes tens of GPU-hours, and combining methods from different codebases means porting each to the new architecture by hand. We present QDA, a system in which an agent designs the recipe for each model and precision. To make evaluation fast, QDA scores each candidate in minutes by its output KL divergence from the original model on reasoning traces that the agent never sees, and checks promising ones with long generations to catch failures such as repetition loops. To make building fast, QDA provides a library of public PTQ methods that are compatible with one another and with new model architectures. Across four reasoning models, QDA improves accuracy over the strongest public recipe by 0.9, 1.4 and 2.2 percentage points on average at W4A16, W4A8 and W3A16, using 64 GPU-hours per search. On the 320B-parameter MoE model GLM-5.3-Flash at NVFP4 W4A4, it recovers 98.3% of the FP8 model's accuracy, against 96.9% for the best vendor checkpoint. Every QDA checkpoint also runs on existing serving kernels with no inference overhead. We will release the library, the evaluator and the harness.

  • Across four reasoning models, QDA improves accuracy over the strongest public recipe by 0.9, 1.4 and 2.2 percentage points on average at W4A16, W4A8 and W3A16, using 64 GPU-hours per search.
  • Across four reasoning models, QDA improves accuracy over the strongest public recipe by 0.9, 1.4 and 2.2 percentage points on average at W4A16, W4A8 and W3A16, using 64 GPU-hours per search.
  • On the 320B-parameter MoE model GLM-5.3-Flash at NVFP4 W4A4, it recovers 98.3% of the FP8 model's accuracy, against 96.9% for the best vendor checkpoint.
  • Every QDA checkpoint also runs on existing serving kernels with no inference overhead.
15

PostgreSQL 19 Released

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Simon Willison 1 bài viết · Simon Willison
Nguyên văn nguồn
Chi tiết nguồn

<p><strong><a href="https://www.postgresql.org/about/news/postgresql-19-released-3449/">PostgreSQL 19 Released</a></strong></p> Most years PostgreSQL ships a new release in September, but this year's release came two months later <a href="https://rhaas.blogspot.com/2026/10/postgres-19-is-late-and-its-ais-fault.html">thanks mainly</a> to the flurry of issues that the PostgreSQL team needed to address as part of the ongoing AI-reported vulnerability apocalypse.</p> <p>This release was definitely worth the wait. My favorite new feature is this one:</p> <blockquote> <p>For applications that send reads to standbys, PostgreSQL 19 adds "read-your-writes" consistency with the new <a href="https://www.postgresql.org/docs/19/sql-wait.html"><code>WAIT FOR LSN</code></a> command. A session on a standby can use <code>WAIT FOR LSN</code> to wait until the standby has replayed the write-ahead log (WAL) up to a specific <a href="https://www.postgresql.org/docs/19/wal-internals.html">log sequence number (LSN)</a> before running a query, so the application can read data it just wrote on the primary.</p> </blockquote> <p>In practice, that looks like this:</p> <pre><code>UPDATE movie SET genre = 'Dramatic' WHERE genre = 'Drama'; SELECT pg_current_wal_insert_lsn(); </code></pre> <p>That returns a value like <code>0/0306EE20</code>. Store that somewhere (a signed cookie would work) such that on a subsequent request your application can do:</p> <pre><code>WAIT FOR LSN '0/0306EE20' WITH (TIMEOUT '0.1s'); SELECT * FROM movie WHERE genre = 'Drama'; </code></pre> <p>The timeout is optional - if you provide one you'll get an error if the replica you are talking to doesn't catch up within the specified time.</p> <p>I first encountered this pattern <a href="https://www.mediawiki.org/wiki/Manual:Database_access#Lag">in Wikipedia</a>, which has a hand-rolled version of this built against MySQL replication:</p> <blockquote> <p>In addition to this, MediaWiki attempts to ensure that the user sees events occurring on the wiki in chronological order. A few seconds of lag can be tolerated, as long as the user sees a consistent picture from subsequent requests. This is done by saving the primary binlog position in the session, and then at the start of each request, waiting for the replica to catch up to that position before doing any reads from it.</p> </blockquote> <p>Here's <a href="https://github.com/wikimedia/mediawiki/blob/1ff78194b182ee4b5b3678f7d9fc9aefd0852cf7/includes/libs/Rdbms/Replication/MysqlReplicationReporter.php#L238-L299">the relevant MediaWiki code</a>, which these days uses MySQL's <a href="https://dev.mysql.com/doc/refman/9.7/en/gtid-functions.html#function_wait-for-executed-gtid-set">WAIT_FOR_EXECUTED_GTID_SET()</a> function and falls back to <a href="https://dev.mysql.com/doc/refman/8.4/en/replication-functions-synchronization.html#function_master-pos-wait">MASTER_POS_WAIT()</a>. <p><small></small>Via <a href="https://lobste.rs/s/pqyuhk/postgresql_19_released">Lobste.rs</a></small></p> <p>Tags: <a href="https://simonwillison.net/tags/mysql">mysql</a>, <a href="https://simonwillison.net/tags/postgresql">postgresql</a>, <a href="https://simonwillison.net/tags/replication">replication</a>, <a href="https://simonwillison.net/tags/scaling">scaling</a>, <a href="https://simonwillison.net/tags/wikipedia">wikipedia</a>, <a href="https://simonwillison.net/tags/ai-security-research">ai-security-research</a></p>

16

Compare the Gemini 4 models with other leading models at: https://artificialanalysis.ai/models/comparisons/gemini-4-neon-vs-gemini-4-carbon

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Compare the Gemini 4 models with other leading models at: https://artificialanalysis.ai/models/comparisons/gemini-4-neon-vs-gemini-4-carbon

17

Neon and Hydrogen occupy all of the Pareto frontiers of Intelligence vs. Cost per Task and Intelligence vs. Time per Task among the three models.

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Neon and Hydrogen occupy all of the Pareto frontiers of Intelligence vs. Cost per Task and Intelligence vs. Time per Task among the three models. Between the two, they scale from an Intelligence Index of 27 at $0.29 per task (Hydrogen, low) to 61 at $6.44 per task (Neon, xhigh). Developers have a lot of flexibility to tune for their use cases with effort level. Carbon does not follow this trend, with relatively little difference in Time or Cost per Task between effort levels. Media

18

Out of your element with the new Gemini 4 releases? Here are some key highlights on Gemini 4 Carbon, Neon and Hydrogen

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Out of your element with the new Gemini 4 releases? Here are some key highlights on Gemini 4 Carbon, Neon and Hydrogen Carbon is the highest-priced model ($4/$20 per 1M input/output tokens), followed by Neon ($3/$15) and Hydrogen ($1.50/$7.50). At low effort, Carbon performs the best of the three but uses more tokens. However, Neon and Hydrogen scale more effectively to higher reasoning efforts and have an additional reasoning option (xhigh). Media

19

Reducing Rollout Bottlenecks in Reinforcement Learning with NVIDIA Dynamo

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Amr Elmeleegy 1 bài viết · NVIDIA Developer Blog
Nguyên văn nguồn
Chi tiết nguồn

Reinforcement learning (RL) uses rewards to train models to solve problems and complete tasks more successfully. Inference drives this process. Workers generate... Reinforcement learning (RL) uses rewards to train models to solve problems and complete tasks more successfully. Inference drives this process. Workers generate rollouts: sequences of model outputs, actions, and environment interactions. The RL framework scores the results, updates model weights, and sends those weights back to the workers for the next round. As RL training scales… Source

20

Crazy how fast you can pull these things together now.

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

fofrai 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Crazy how fast you can pull these things together now. Neon: > Take the monstera character pixel art and turn it into something more of a high-fidelity 3D concept that I can walk around a midcentury modern room Media

1–20 / 96
Trang 1 / 5