FTrace parsing slow on large traces
Created by: bjackman
The example trace (220Mb) used by Lisa's Trappy tutorial notebook takes 15-20 seconds to parse on my machine (Xeon Sandy Bridge, E5-1660). That seems like it might be a regression. Should figure out what's taking up all the time.
Events parsed are:
"sched_switch",
"sched_wakeup",
"sched_contrib_scale_f",
"sched_load_avg_cpu",
"sched_load_avg_task",
"sched_tune_tasks_update",
"sched_boost_cpu",
"sched_boost_task",
"sched_energy_diff",
"sched_overutilized",
"cpu_frequency",
"cpu_capacity"