You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the cudf.pandas.Profiler uses sys.settrace to profile lines or cudf.pandas fast-slow calls. Currently the downsides of this approach is:
The tracing function is called for every frame while we're only interested in certain events (line and function calls) providing unnecessary overhead otherwise.
Maintaining some complexity in a monolithic tracing function.
Additionally we may find opportunities to improve profiling performance by disabling the profiling by having the callback return sys.monitoring.DISABLE.
Describe alternatives you've considered
Status quo
The text was updated successfully, but these errors were encountered:
mroeschke
changed the title
[FEA] Implemented cudf.pandas Profiler using sys.monitoring
[FEA] Implement cudf.pandas Profiler using sys.monitoring
Dec 4, 2024
Is your feature request related to a problem? Please describe.
Currently the
cudf.pandas.Profiler
usessys.settrace
to profile lines or cudf.pandas fast-slow calls. Currently the downsides of this approach is:Describe the solution you'd like
The
sys.monitoring
namespace, a new Python 3.12 feature, should be able to address both downsides: https://docs.python.org/3/library/sys.monitoring.htmlsys.monitoring.events.LINE
,sys.monitoring.events.CALL
)Additionally we may find opportunities to improve profiling performance by disabling the profiling by having the callback return
sys.monitoring.DISABLE
.Describe alternatives you've considered
Status quo
The text was updated successfully, but these errors were encountered: