2022-02-11 09:07:11 +11:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0-or-later */
|
2020-04-22 12:53:47 +02:00
|
|
|
|
|
|
|
|
#include "BLI_timeit.hh"
|
|
|
|
|
|
2022-03-23 23:35:23 -05:00
|
|
|
#include <algorithm>
|
IO: print import & export times of Alembic & USD
Many existing importers/exporters do log the time it takes to system
console (some others log more information too). In particular, OBJ
(C++ & python), STL (C++ & python), PLY, glTF2 all log the time it
takes. However, neither USD nor Alembic do. And also it's harder to
know the time it takes there from a profiler, since all the work
normally is done on a background job and is split between several
threads (so you can't just find some top-level function and see how
much time it took).
This change:
- Adds import/export time logging to USD & Alembic importer/exporter,
- In the time utility class (also used by OBJ & STL), improve the
output formatting: 1) print only one decimal digit, 2) for long
times, print seconds and also produce a hours:minutes:seconds form.
Reviewed By: Michael Kowalski, Kévin Dietrich
Differential Revision: https://developer.blender.org/D15170
2022-07-01 12:17:50 +03:00
|
|
|
#include <iomanip>
|
2022-03-23 23:35:23 -05:00
|
|
|
|
2020-07-06 12:37:11 +02:00
|
|
|
namespace blender::timeit {
|
2020-04-22 12:53:47 +02:00
|
|
|
|
|
|
|
|
void print_duration(Nanoseconds duration)
|
|
|
|
|
{
|
IO: print import & export times of Alembic & USD
Many existing importers/exporters do log the time it takes to system
console (some others log more information too). In particular, OBJ
(C++ & python), STL (C++ & python), PLY, glTF2 all log the time it
takes. However, neither USD nor Alembic do. And also it's harder to
know the time it takes there from a profiler, since all the work
normally is done on a background job and is split between several
threads (so you can't just find some top-level function and see how
much time it took).
This change:
- Adds import/export time logging to USD & Alembic importer/exporter,
- In the time utility class (also used by OBJ & STL), improve the
output formatting: 1) print only one decimal digit, 2) for long
times, print seconds and also produce a hours:minutes:seconds form.
Reviewed By: Michael Kowalski, Kévin Dietrich
Differential Revision: https://developer.blender.org/D15170
2022-07-01 12:17:50 +03:00
|
|
|
using namespace std::chrono;
|
|
|
|
|
if (duration < microseconds(100)) {
|
2020-04-22 12:53:47 +02:00
|
|
|
std::cout << duration.count() << " ns";
|
|
|
|
|
}
|
IO: print import & export times of Alembic & USD
Many existing importers/exporters do log the time it takes to system
console (some others log more information too). In particular, OBJ
(C++ & python), STL (C++ & python), PLY, glTF2 all log the time it
takes. However, neither USD nor Alembic do. And also it's harder to
know the time it takes there from a profiler, since all the work
normally is done on a background job and is split between several
threads (so you can't just find some top-level function and see how
much time it took).
This change:
- Adds import/export time logging to USD & Alembic importer/exporter,
- In the time utility class (also used by OBJ & STL), improve the
output formatting: 1) print only one decimal digit, 2) for long
times, print seconds and also produce a hours:minutes:seconds form.
Reviewed By: Michael Kowalski, Kévin Dietrich
Differential Revision: https://developer.blender.org/D15170
2022-07-01 12:17:50 +03:00
|
|
|
else if (duration < seconds(5)) {
|
|
|
|
|
std::cout << std::fixed << std::setprecision(1) << duration.count() / 1.0e6 << " ms";
|
|
|
|
|
}
|
|
|
|
|
else if (duration > seconds(90)) {
|
|
|
|
|
/* Long durations: print seconds, and also H:m:s */
|
|
|
|
|
const auto dur_hours = duration_cast<hours>(duration);
|
|
|
|
|
const auto dur_mins = duration_cast<minutes>(duration - dur_hours);
|
|
|
|
|
const auto dur_sec = duration_cast<seconds>(duration - dur_hours - dur_mins);
|
|
|
|
|
std::cout << std::fixed << std::setprecision(1) << duration.count() / 1.0e9 << " s ("
|
|
|
|
|
<< dur_hours.count() << "H:" << dur_mins.count() << "m:" << dur_sec.count() << "s)";
|
2020-04-22 12:53:47 +02:00
|
|
|
}
|
|
|
|
|
else {
|
IO: print import & export times of Alembic & USD
Many existing importers/exporters do log the time it takes to system
console (some others log more information too). In particular, OBJ
(C++ & python), STL (C++ & python), PLY, glTF2 all log the time it
takes. However, neither USD nor Alembic do. And also it's harder to
know the time it takes there from a profiler, since all the work
normally is done on a background job and is split between several
threads (so you can't just find some top-level function and see how
much time it took).
This change:
- Adds import/export time logging to USD & Alembic importer/exporter,
- In the time utility class (also used by OBJ & STL), improve the
output formatting: 1) print only one decimal digit, 2) for long
times, print seconds and also produce a hours:minutes:seconds form.
Reviewed By: Michael Kowalski, Kévin Dietrich
Differential Revision: https://developer.blender.org/D15170
2022-07-01 12:17:50 +03:00
|
|
|
std::cout << std::fixed << std::setprecision(1) << duration.count() / 1.0e9 << " s";
|
2020-04-22 12:53:47 +02:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2022-03-23 23:35:23 -05:00
|
|
|
ScopedTimerAveraged::~ScopedTimerAveraged()
|
|
|
|
|
{
|
|
|
|
|
const TimePoint end = Clock::now();
|
|
|
|
|
const Nanoseconds duration = end - start_;
|
|
|
|
|
|
|
|
|
|
total_count_++;
|
|
|
|
|
total_time_ += duration;
|
|
|
|
|
min_time_ = std::min(duration, min_time_);
|
|
|
|
|
|
|
|
|
|
std::cout << "Timer '" << name_ << "': (Average: ";
|
|
|
|
|
print_duration(total_time_ / total_count_);
|
|
|
|
|
std::cout << ", Min: ";
|
|
|
|
|
print_duration(min_time_);
|
|
|
|
|
std::cout << ")\n";
|
|
|
|
|
}
|
|
|
|
|
|
2020-07-06 12:37:11 +02:00
|
|
|
} // namespace blender::timeit
|