Open verdie-g opened 2 months ago
Building the tree only takes a second or two in the worse cases. It appears that the issue is to render the TreeView. Let's see in https://github.com/microsoft/fluentui-blazor/issues/1855 if there is some performance opportunities there.
In a future .NET's multi-threading will work in WASM: https://github.com/dotnet/runtime/issues/68162.
Since https://github.com/verdie-g/dotnet-events-viewer/commit/b8a313b602ee2e8f75e003d694761f0e5e567d94 it seems like the filtering can take several seconds to execute. So, that filtering could be done in a worker for a better experience. Though, workers have a shared-nothing design, sharing data is only done through message passing. Passing the trace to a worker would mean serializing gigabytes of data.
To avoid blocking the UI. https://github.com/Tewr/BlazorWorker could help.