Skip to content
GitHub Explorer

xparq/iprof

View on GitHub ↗Related repositories →

A pretty simple and performant C++ profiling library

active 2023-10-03 → 2024-02-18 (UTC)

Complete coverage26,772 / 26,772 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-09-03 (UTC)
Events
64
Pushes
21
Pull requests
0
Issues
34
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 139 days from 2023-10-03 to 2024-02-18. Pushes: 21 total, peak 10 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 34 total, peak 16 in a day. Comments: 7 total, peak 5 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
xparq622107

Recent activity

Latest issues, pull requests and releases

  • Issue#24xparq2024-02-18 19:29
    Possible static init issue?
  • Issue#23xparq2023-10-06 20:39
    Readme: put the include path back
  • Issue#22xparq2023-10-06 10:48
    Unscoped (unbalanced) start/stop pairs to measure specific code paths
  • Issue#21xparq2023-10-06 09:59
    Consolidate the (function) naming convention (e.g. Start/Stop vs. all the lame camelCase)
  • Issue#20xparq2023-10-06 09:14
    Extend Accumulate...() with a predictive meas. vector resize
  • Issue#19xparq2023-10-06 09:06
    Why the loop in Stop? When is it not just the last item?
  • Issue comment#19xparq2023-10-06 09:05
    Why the loop in Stop? When is it not just the last item?
  • Issue#19xparq2023-10-05 23:30
    Why the loop in Stop? When is it not just the last item?
  • Issue#18xparq2023-10-05 22:32
    Why exactly is Start/Stop not members of ScopedMeasure?
  • Issue#17xparq2023-10-05 21:46
    Document what would happen if IPROF_SYNC would never be called
  • Issue#16xparq2023-10-05 19:34
    Merge IPROF_SYNC into IPROF_SYNC_THREAD?
  • Issue#15xparq2023-10-05 18:56
    Understand why the unprofiled tests (in #12) actually take longer! :-o
  • Issue#14xparq2023-10-05 17:00
    Shouldn't just IPROF_SYNC_THREAD recommended in this README section?
  • Issue comment#13xparq2023-10-05 01:02
    test.cpp: Crash with w64devkit...
  • Issue#13xparq2023-10-05 01:02
    test.cpp: Crash with w64devkit...
  • Issue comment#13xparq2023-10-04 20:59
    test.cpp: Crash with w64devkit when running without iprof...
  • Issue#13xparq2023-10-04 19:56
    test.cpp: Crash with w64devkit when running without iprof...
  • Issue#12xparq2023-10-04 19:30
    Duplicate the tests in test.cpp with and without IPROF_DISABLE, and compare the overall times!
  • Issue comment#12xparq2023-10-04 19:21
    Duplicate the tests in test.cpp with and without IPROF_DISABLE, and compare the overall times!
  • Issue#11xparq2023-10-04 18:59
    Make hitime.hpp an internal part of iProf, while and also include-able alone!
  • Issue#6xparq2023-10-04 18:59
    ...SECS(x) macros -> inline functions
  • Issue#5xparq2023-10-04 18:53
    Make test.cpp runnable also with IPROF_DISABLE
  • Issue comment#8xparq2023-10-04 18:07
    Move HighResClock into the iProf namespace
  • Issue#11xparq2023-10-04 18:06
    Make hitime.hpp an internal part of iProf, while and also include-able alone!
  • Issue#10xparq2023-10-04 16:47
    Sort out the various flavors of stats in multi-threaded runs!

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.