Skip to content

docstr to explaing >100% compilation time in @time #47980

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

docstr to explaing >100% compilation time in @time #47980

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b8e1007
docstr to explaing >100% compilation time in @time
Krastanov Dec 23, 2022
ff2eba3
expand docstring of @elapsed and @timed
Krastanov Dec 23, 2022
1f562c3
better phrasing
Krastanov Dec 23, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions base/timing.jl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -216,7 +216,9 @@ Optionally provide a description string to print before the time report.

In some cases the system will look inside the `@time` expression and compile some of the
called code before execution of the top-level expression begins. When that happens, some
compilation time will not be counted. To include this time you can run `@time @eval ...`.
compilation time will not be counted in the total, but may still be counted in the
reported percentage, potentially even resulting in compilation times >100%. To report
this time more accurately, you can run `@time @eval ...`.

See also [`@showtime`](@ref), [`@timev`](@ref), [`@timed`](@ref), [`@elapsed`](@ref),
[`@allocated`](@ref), and [`@allocations`](@ref).
Expand Down Expand Up @@ -376,7 +378,9 @@ number of seconds it took to execute as a floating-point number.

In some cases the system will look inside the `@elapsed` expression and compile some of the
called code before execution of the top-level expression begins. When that happens, some
compilation time will not be counted. To include this time you can run `@elapsed @eval ...`.
compilation time will not be counted in the total, but may still be counted in the
reported percentage, potentially even resulting in compilation times >100%. To report
this time more accurately, you can run `@elapsed @eval ...`.

See also [`@time`](@ref), [`@timev`](@ref), [`@timed`](@ref),
[`@allocated`](@ref), and [`@allocations`](@ref).
Expand Down Expand Up @@ -466,7 +470,9 @@ counters.

In some cases the system will look inside the `@timed` expression and compile some of the
called code before execution of the top-level expression begins. When that happens, some
compilation time will not be counted. To include this time you can run `@timed @eval ...`.
compilation time will not be counted in the total, but may still be counted in the
reported percentage, potentially even resulting in compilation times >100%. To report
this time more accurately, you can run `@timed @eval ...`.

See also [`@time`](@ref), [`@timev`](@ref), [`@elapsed`](@ref),
[`@allocated`](@ref), and [`@allocations`](@ref).
Expand Down