ui: support searching int args

[altimin]

and also make it faster.

The current implementation takes ~250ms on example Chrome trace:

select
  slice_id as sliceId,
  ts,
  'slice' as source,
  track_id as sourceId,
  0 as utid
from slice
join args using(arg_set_id)
where string_value glob '*[mM][aA][iI][nN]*' or key glob '*[mM][aA][iI][nN]*'

Naive support for ints would take ~320ms:

select
  slice_id as sliceId,
  ts,
  'slice' as source,
  track_id as sourceId,
  0 as utid
from slice
join args using(arg_set_id)
where display_value glob '*[mM][aA][iI][nN]*' or key glob '*[mM][aA][iI][nN]*'

This patch filters args first, taking the total time down to 90ms:

select
  slice_id as sliceId,
  ts,
  'slice' as source,
  track_id as sourceId,
  0 as utid
from slice
join (
  select arg_set_id from args where display_value glob '*[mM][aA][iI][nN]*'
  union
  select arg_set_id from args where key glob '*[mM][aA][iI][nN]*'
) using (arg_set_id)

[github-actions]

🎨 Perfetto UI Build

✅ UI build is ready: https://storage.googleapis.com/perfetto-ci-artifacts/gh-19682425044-ui/ui/index.html

[stevegolton]

Can we park this for now. We have some concerns:

• How display_value scales, IIUC it's an SQL expression.
• The optimization is a hack based on the current foibles of the query planner.

@LalitMaganti knows more.