<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Core technologies on TauGrid</title><link>https://azure.github.io/taugrid/docs/getting-started/core-technologies/</link><description>Recent content in Core technologies on TauGrid</description><generator>Hugo</generator><language>en</language><atom:link href="https://azure.github.io/taugrid/docs/getting-started/core-technologies/index.xml" rel="self" type="application/rss+xml"/><item><title>What is Ray?</title><link>https://azure.github.io/taugrid/docs/getting-started/core-technologies/ray/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://azure.github.io/taugrid/docs/getting-started/core-technologies/ray/</guid><description>&lt;p&gt;&lt;a href="https://www.ray.io/"&gt;Ray&lt;/a&gt; is an open-source framework for running Python work
across processes and machines. Teams use it for distributed training,
hyperparameter tuning, data processing, and model serving.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://ray-project.github.io/kuberay/"&gt;KubeRay&lt;/a&gt; brings Ray to Kubernetes. Its
operator manages resources such as &lt;code&gt;RayJob&lt;/code&gt; and &lt;code&gt;RayService&lt;/code&gt;, creates the Ray
head and worker pods, and follows the Ray workload lifecycle.&lt;/p&gt;
&lt;h2 id="how-taugrid-uses-ray"&gt;How TauGrid uses Ray&lt;/h2&gt;
&lt;p&gt;TauGrid turns a repository target into either a Kubernetes &lt;code&gt;Job&lt;/code&gt; or a KubeRay
&lt;code&gt;RayJob&lt;/code&gt;. A Ray workload follows this path:&lt;/p&gt;</description></item><item><title>What is Kueue?</title><link>https://azure.github.io/taugrid/docs/getting-started/core-technologies/kueue/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://azure.github.io/taugrid/docs/getting-started/core-technologies/kueue/</guid><description>&lt;p&gt;&lt;a href="https://kueue.sigs.k8s.io/"&gt;Kueue&lt;/a&gt; is a Kubernetes-native queue and admission
system for batch and AI workloads. It decides when a workload may consume
shared quota. After admission, the Kubernetes scheduler decides which nodes run
the pods.&lt;/p&gt;
&lt;h2 id="the-main-kueue-objects"&gt;The main Kueue objects&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A &lt;code&gt;LocalQueue&lt;/code&gt; is the queue a workspace submits to.&lt;/li&gt;
&lt;li&gt;A &lt;code&gt;ClusterQueue&lt;/code&gt; combines quota across one or more LocalQueues.&lt;/li&gt;
&lt;li&gt;A &lt;code&gt;ResourceFlavor&lt;/code&gt; describes a class of capacity, such as CPU nodes or a
particular GPU class.&lt;/li&gt;
&lt;li&gt;A &lt;code&gt;Workload&lt;/code&gt; records the resources a Job or RayJob requests and its admission
state.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;TauGrid resolves the workspace LocalQueue and adds it to the rendered workload.
Kueue then evaluates quota, priority, queue order, and resource flavors.&lt;/p&gt;</description></item><item><title>What is adx-mon?</title><link>https://azure.github.io/taugrid/docs/getting-started/core-technologies/adx-mon/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://azure.github.io/taugrid/docs/getting-started/core-technologies/adx-mon/</guid><description>&lt;p&gt;&lt;a href="https://github.com/Azure/adx-mon"&gt;adx-mon&lt;/a&gt; is Azure Data Explorer Monitor, an
observability pipeline for Kubernetes clusters. It collects metrics, logs, and
GPU telemetry, batches the data, and sends it to Azure Data Explorer
(ADX/Kusto).&lt;/p&gt;
&lt;p&gt;Its main components collect node and cluster signals, ingest batches into ADX,
manage ADX schema commands, and evaluate configured alerts. Platform teams
choose the signals, databases, retention, identities, and access rules.&lt;/p&gt;
&lt;h2 id="how-taugrid-uses-adx-mon"&gt;How TauGrid uses adx-mon&lt;/h2&gt;
&lt;p&gt;adx-mon is an optional platform integration. A TauGrid environment can use it
to:&lt;/p&gt;</description></item><item><title>What is Stellar?</title><link>https://azure.github.io/taugrid/docs/getting-started/core-technologies/stellar/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://azure.github.io/taugrid/docs/getting-started/core-technologies/stellar/</guid><description>&lt;p&gt;Stellar is TauGrid&amp;rsquo;s experiment tracking and comparison experience. It ships in
the &lt;code&gt;taugrid-portal&lt;/code&gt; binary and presents run details, scalar metric history, and
side-by-side comparisons in a browser or terminal.&lt;/p&gt;
&lt;h2 id="what-stellar-helps-answer"&gt;What Stellar helps answer&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Which code and settings produced this run?&lt;/li&gt;
&lt;li&gt;How did loss, accuracy, throughput, or another metric change over time?&lt;/li&gt;
&lt;li&gt;Which run performed best?&lt;/li&gt;
&lt;li&gt;Where are the model, checkpoint, and other output files?&lt;/li&gt;
&lt;li&gt;Did the run finish, retry, or resume?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="where-the-data-comes-from"&gt;Where the data comes from&lt;/h2&gt;
&lt;p&gt;TauGrid saves complete metric files and a small experiment index close to the
run. Stellar can read that saved evidence directly. A platform can also provide
an ADX/Kusto view for searching and comparing runs across workspaces.&lt;/p&gt;</description></item></channel></rss>