Meta tags:
description= Namespace accelerates the development workflow of fast-moving software engineering teams. Best-in-class compute and development-supporting services that lead to 2x-10x faster builds, tests, and more.;
Headings (most frequently used words):
usage, memory, step, optimizing, resource, insights, finding, optimization, opportunities, generating, an, over, provisioned, report, best, practices, related, documentation, introducing, devboxes, we, re, hiring, join, us, view, peak, filter, out, high, jobs, verify, cpu, underutilization,
Text of the page (most frequently used words):
nsc (75), usage (20), github (19), the (18), and (16), jobs (14), #memory (13), docker (11), job (10), actions (10), for (9), resource (9), list (9), registry (9), artifact (9), performance (8), your (8), setup (8), machine (7), base (7), optimization (7), instance (7), cpu (7), cache (7), profile (7), namespacelabs (7), shapes (6), insights (6), report (6), that (6), image (6), describe (6), action (6), nscloud (6), overview (6), with (5), images (5), opportunities (5), over (5), under (5), view (5), namespace (5), token (5), optimize (4), build (4), remote (4), caching (4), custom (4), dashboard (4), use (4), peak (4), this (4), you (4), login (4), vault (4), upload (4), buildx (4), runner (3), builds (3), reduce (3), time (3), test (3), low (3), candidates (3), smaller (3), shape (3), run (3), display (3), filter (3), out (3), resources (3), optimizing (3), create (3), auth (3), update (3), download (3), ingress (3), expose (3), kubernetes (3), container (3), devboxes (3), started (3), last (2), cost (2), builders (2), high (2), dependencies (2), visibility (2), into (2), how (2), impact (2), costs (2), changes (2), making (2), data (2), produce (2), same (2), csv (2), provisioned (2), than (2), these (2), across (2), workspace (2), allocated (2), both (2), can (2), more (2), show (2), are (2), check (2), utilize (2), their (2), max (2), step (2), only (2), windows (2), linux (2), click (2), have (2), alt (2), shift (2), down (2), right (2), per (2), change (2), set (2), default (2), all (2), back (2), status (2), trust (2), generate (2), delete (2), sccache (2), pants (2), gradle (2), bazel (2), expiration (2), extend (2), volume (2), git (2), checkout (2), access (2), ssh (2), logs (2), circleci (2), security (2), limits (2), storage (2), getting (2), logo (2), open (2), updated, july, 2026, configure, settings, optimal, efficiency, advanced, configuration, strategies, pre, install, startup, utilization, implement, cross, invocation, artifacts, execution, solutions, related, documentation, updates, automatically, providing, real, efforts, feature, branches, different, safely, configurations, make, incremental, measure, gradual, establish, baselines, before, baseline, review, weekly, identify, regular, monitoring, best, practices, based, historical, days, obtained, via, short, name, consistent, within, category, pair, favourite, llm, agent, surface, following, prompt, works, well, starting, point, larger, they, actually, need, paying, goes, unused, command, export, every, including, observed, generating, consistently, running, likely, moved, effective, without, impacting, prime, also, now, switch, verify, underutilization, keep, doing, until, left, will, type, ctrl, cmd, too, many, through, easily, them, finding, narrow, filters, hit, least, one, leaving, utilized, potential, shows, easy, spot, used, percentage, breakdown, should, see, values, sequential, navigate, each, provides, detailed, workflow, consumption, monitor, built, understanding, workflows, consume, helps, select, while, maintaining, support, center, soc2, changelog, revoke, relationships, dev, add, policy, share, url, expire, release, submodules, cleanup, attach, context, kubectl, kubeconfig, write, port, forward, proxy, rdp, vnc, top, destroy, version, installation, cli, turbocache, breakpoint, cluster, api, sdk, explorer, rwx, openid, gcp, aws, federation, permissions, audit, logging, residency, billing, workspaces, egress, filtering, networking, secrets, volumes, observability, macos, compute, any, framework, tailscale, claude, checkouts, nix, moonrepo, android, emulators, playwright, turborepo, integrations, coding, agents, sessions, development, managing, introduction, containers, previews, tracing, reference, migration, guide, debugging, roles, hiring, join, read, article, introducing, sidebar, get, company, pricing, customers, cases,
Text of the page (random words):
optimizing usage namespace logo use cases customers pricing resources company get started login open sidebar introducing devboxes read article we re hiring join us open roles logo overview github actions getting started caching docker builds custom base images debugging github actions migration guide optimizing usage reference docker builders getting started container registry tracing logs previews containers kubernetes devboxes introduction managing devboxes remote development sessions custom images coding agents integrations bazel turborepo playwright android emulators gradle sccache circleci pants moonrepo nix git checkouts docker images claude tailscale any framework compute overview linux macos windows observability ssh remote display machine shapes resource limits storage overview cache volumes container registry artifact storage secrets networking overview ingress performance security egress filtering workspaces overview access billing and limits data residency security audit logging permissions federation overview aws gcp openid github actions circleci rwx dashboard github actions builds registry usage explorer api sdk github actions namespacelabs nscloud setup namespacelabs nscloud setup buildx action namespacelabs nscloud cluster action namespacelabs nscloud cache action namespacelabs nscloud checkout action namespacelabs nscloud expose kubernetes action namespace actions upload artifact namespace actions download artifact namespacelabs breakpoint action namespace actions setup turbocache cli installation nsc version nsc login nsc workspace describe nsc create nsc destroy nsc extend nsc list nsc instance report nsc logs nsc top nsc ssh nsc vnc nsc rdp nsc proxy nsc instance port forward nsc instance download nsc instance upload nsc kubeconfig write nsc kubectl nsc docker login nsc docker attach context nsc docker remote nsc docker buildx setup nsc docker buildx cleanup nsc docker buildx status nsc build nsc base image upload nsc base image optimize nsc run nsc expose container nsc expose kubernetes nsc ingress list nsc ingress generate access token nsc github profile nsc github profile create nsc github profile list nsc github profile describe nsc github profile update nsc github profile delete nsc github profile test build base image nsc github base image list nsc github base image describe nsc github job list nsc github job describe nsc git checkout update submodules nsc volume list nsc volume release nsc artifact upload nsc artifact download nsc artifact expire nsc artifact extend nsc artifact describe nsc artifact cache url nsc registry list nsc registry describe nsc registry share nsc registry update image expiration nsc registry policy nsc registry default expiration nsc cache bazel setup nsc cache gradle setup nsc cache pants setup nsc cache sccache setup nsc vault list nsc vault add nsc vault set nsc vault delete nsc auth check login nsc auth generate dev token nsc auth trust relationships nsc token create nsc token list nsc token revoke changelog trust center soc2 status support optimizing usage monitor and optimize your github actions resource usage with namespace s built in insights dashboard understanding how your workflows consume resources helps you select the right machine shapes and reduce costs while maintaining performance resource usage insights the insights dashboard provides detailed visibility into your workflow resource consumption across all your jobs view peak memory usage to view the peak memory usage for each job navigate to github actions insights change the view to sequential to see all job values back to back set breakdown to job should be the default change display to max memory used per job percentage this view shows peak memory usage per job making it easy to spot jobs that over or under utilize their allocated resources to narrow down the view to jobs with low memory usage click show optimization potential this filters out jobs that hit over 50 memory in at least one run leaving only the under utilized candidates finding optimization opportunities if you have too many jobs to go through you can easily filter them down to the right opportunities step 1 filter out high memory usage jobs use alt shift cmd or alt shift ctrl on windows linux to click on jobs that have more than 50 memory usage this will filter that job type out keep doing this until you re only left with jobs under 50 memory usage these are your optimization opportunities step 2 verify cpu underutilization now switch the display to max cpu usage check if the same jobs also under utilize their cpu jobs that show both low memory and cpu usage are prime candidates for smaller machine shapes jobs consistently running under 50 for both cpu and memory usage can likely be moved to smaller more cost effective machine shapes without impacting performance generating an over provisioned report over provisioned jobs run on a machine shape larger than they actually need paying for cpu and memory that goes unused to produce a report of these jobs across your workspace use the nsc instance report command to export a csv of every runner instance including the allocated shape and the observed peak cpu and memory usage pair the csv with your favourite llm agent to surface candidates for a smaller shape the following prompt works well as a starting point based on github job historical data over the last 7 days obtained via nsc instance report produce a short report of resource optimization opportunities for jobs for the same job name consistent low resource usage within a category best practices regular monitoring review insights weekly to identify optimization opportunities baseline performance establish performance baselines before making changes gradual optimization make incremental changes and measure impact test configurations use feature branches to test different machine shapes safely the insights dashboard updates automatically providing real time visibility into how your optimization efforts impact resource usage and costs related documentation caching solutions implement cross invocation caching for dependencies and build artifacts to reduce execution time and resource usage custom base images pre install dependencies in custom runner images to reduce startup time and optimize resource utilization high performance docker builds optimize docker build performance with remote builders and caching strategies advanced configuration configure machine shapes and runner settings for optimal performance and cost efficiency last updated july 3 2026
|