RunMat
  • Pricing
RunMat
GitHub
GitHub
Sign inTry in browser
DesktopRuntimePhysicsCADAdministrationAgent

Get RunMat updates

New releases, guides and examples.

Product+
  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download
Math+
  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting
Physics+
  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA
Industries+
  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance
Learn+
  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students
Compare+
  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons
Company+
  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms

Product

  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download

Math

  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting

Physics

  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA

Industries

  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance

Learn

  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students

Compare

  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons

Company

  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms
GitHubXLinkedIn

© Dystr, Inc. · RunMat v0.7.1, Nov 17, 2026

RunMat® is a registered trademark of Dystr, Inc. MATLAB® is a registered trademark of The MathWorks, Inc. RunMat is not affiliated with, endorsed by, or sponsored by The MathWorks, Inc.

/
See all docs
Builtin Reference
    • cputime
    • pause
    • set.BusyMode
    • set.ErrorFcn
    • set.ExecutionMode
    • set.Name
    • set.ObjectVisibility
    • set.Period
    • set.StartDelay
    • set.StartFcn
    • set.StopFcn
    • set.Tag
    • set.TasksToExecute
    • set.TimerFcn
    • set.UserData
    • tic
    • timeit
    • timer
    • timerfind
    • timerfindall
    • toc

tic — Start a high-resolution session-owned stopwatch.

tic starts a monotonic wall-clock stopwatch. Capture its opaque uint64 token when a later toc(token) must refer to that start; an uncaptured tic only updates the latest start.

Syntax

timerVal = tic()

Returns

timerVal
Type
NumericScalar
Description
Opaque session-owned uint64 stopwatch token used by toc.
NameTypeDescription
timerValNumericScalarOpaque session-owned uint64 stopwatch token used by toc.

Errors

RunMat:tic:ContextUnavailable
When
No invocation timing context is installed.
Message
tic: runtime context is unavailable
RunMat:tic:TokenExhausted
When
The process-local stopwatch token identity space is exhausted.
Message
tic: stopwatch token identity space exhausted
IdentifierWhenMessage
RunMat:tic:ContextUnavailableNo invocation timing context is installed.tic: runtime context is unavailable
RunMat:tic:TokenExhaustedThe process-local stopwatch token identity space is exhausted.tic: stopwatch token identity space exhausted

Behavior

The returned uint64 is an opaque session token, not an encoded timestamp. A token from another session or execution generation is invalid.

tic without an observed output updates only the latest start; repeated statement-form starts do not retain unreachable handles.

tic uses the invocation's monotonic timing service and never enters GPU fusion or provider execution.

Examples

Measuring a simple loop

tic;
for k = 1:1e5
    sqrt(k);
end
elapsed = toc

Capturing and reusing the tic handle

t = tic;
x = sum(1:1000);
elapsed = toc(t)

Nesting timers for staged profiling

outer = tic;
x = sum(1:1000);
inner = tic;
y = sum(1:2000);
innerT = toc(inner);
outerT = toc(outer)

Measuring a suspending wait

token = tic;
pause(0.01);
elapsed = toc(token)

Resetting the stopwatch after a measurement

elapsed1 = toc(tic);
pause(0.1);
elapsed2 = toc(tic)

Using tic with coding agents

Open a RunMat example with live inputs, then ask the agent to explain how tic changes the result.

Run a small tic example, explain the result, then change one input and compare the output.

FAQ

Does tic print anything when called without a semicolon?⌄

No. tic is a sink builtin; the stopwatch token is displayed only when explicitly requested.

Is the returned handle portable across sessions?⌄

No. The opaque token is valid only in its owning RunMat session and cannot be saved for a later session.

Can I run tic on a worker thread?⌄

Yes. Independent runtime contexts own independent stopwatch state; retain explicit tokens when starts may interleave within a context.

How accurate is the measurement?⌄

The monotonic host clock determines resolution; RunMat adds no artificial jitter or throttling.

Does tic participate in GPU fusion?⌄

No. It is a host-side timing boundary.

Related Timing functions

cputime · pause · set.BusyMode · set.ErrorFcn · set.ExecutionMode · set.Name · set.ObjectVisibility · set.Period · set.StartDelay · set.StartFcn · set.StopFcn · set.Tag · set.TasksToExecute · set.TimerFcn · set.UserData · timeit · timer · timerfind · timerfindall · toc

Source you can read

Every RunMat function's source is public. Read exactly how tic is executed, line by line, in Rust.

  • View the source for tic in Rust on GitHub
  • Learn how the RunMat runtime works
  • Found a bug? Open an issue with a minimal reproduction.

About RunMat

RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.

  • RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
  • Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.

Getting started · Benchmarks · Pricing

Download RunMat

Download RunMat for full performance, or use RunMat in your browser for zero setup.

Download RunMatOpen Sandbox
On this page
  • Syntax
  • Returns
  • Errors
  • Behavior
  • Examples
  • Measuring a simple loop
  • Capturing and reusing the tic handle
  • Nesting timers for staged profiling
  • Measuring a suspending wait
  • Resetting the stopwatch after a measurement
  • Using tic with coding agents
  • FAQ
  • Related Timing functions
  • Source you can read
  • About RunMat