pikers
/
piker
3
0
Fork 0
Code Issues 4 Pull Requests 6 Packages Projects Releases Wiki Activity

Add back `.prepareGeometryChange()`, seems faster?

overlays_interaction_latency_tuning
Tyler Goodlet 2023-01-23 15:28:16 -05:00
parent a36d4b1dc6
commit 49ca743e6a
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
piker/ui/_dataviz.py
View File

@ -342,7 +342,7 @@ class Viz(msgspec.Struct): # , frozen=True):
''' '''
name = self.name name = self.name
profiler = Profiler( profiler = Profiler(
msg=f'{name} -> `{str(self)}.maxmin()`', msg=f'`Viz[{name}].maxmin()`',
disabled=not pg_profile_enabled(), disabled=not pg_profile_enabled(),
ms_threshold=4, ms_threshold=4,
delayed=True, delayed=True,
@ -857,15 +857,15 @@ class Viz(msgspec.Struct): # , frozen=True):
# array_key, # array_key,
# index_field=self.index_field, # index_field=self.index_field,
# ) # )
graphics.update()
profiler('.update()')
# TODO: does this actuallly help us in any way (prolly should # TODO: does this actuallly help us in any way (prolly should
# look at the source / ask ogi). I think it avoid artifacts on # look at the source / ask ogi). I think it avoid artifacts on
# wheel-scroll downsampling curve updates? # wheel-scroll downsampling curve updates?
# TODO: is this ever better? # TODO: is this ever better?
# graphics.prepareGeometryChange() graphics.prepareGeometryChange()
# profiler('.prepareGeometryChange()') profiler('.prepareGeometryChange()')
graphics.update()
profiler('.update()')
# track downsampled state # track downsampled state
self._in_ds = r._in_ds self._in_ds = r._in_ds