Databases
StackOverflow2013
Postsdbo
POMore efficient log filter
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMore efficient log filter
    primarykey
    data
    text
    <p>I have a program that displays lines from a log file.</p> <p>They are parsed and put into a class called LogLine then displayed in a datagrid</p> <p>Here is my filter function:</p> <pre><code>ICollectionView view = CollectionViewSource.GetDefaultView(this.LogView.ItemsSource); bool traceChecked = this.TraceCheckbox.IsChecked.HasValue &amp;&amp; this.TraceCheckbox.IsChecked.Value; bool debugChecked = this.DebugCheckbox.IsChecked.HasValue &amp;&amp; this.DebugCheckbox.IsChecked.Value; bool infoChecked = this.InfoCheckbox.IsChecked.HasValue &amp;&amp; this.InfoCheckbox.IsChecked.Value; bool warnChecked = this.WarnCheckbox.IsChecked.HasValue &amp;&amp; this.WarnCheckbox.IsChecked.Value; bool errorChecked = this.ErrorCheckbox.IsChecked.HasValue &amp;&amp; this.ErrorCheckbox.IsChecked.Value; string filtertext = this.TextFilterBox.Text; view.Filter = o =&gt; { LogLine line = o as LogLine; return line != null &amp;&amp; (((traceChecked &amp;&amp; line.Trace) || (debugChecked &amp;&amp; line.Debug) || (infoChecked &amp;&amp; line.Info) || (warnChecked &amp;&amp; line.Warn) || (errorChecked &amp;&amp; line.Error)) &amp;&amp; line.Message.Contains(filtertext)); }; </code></pre> <p>This function is slow, already, taking close to 5 seconds on a log with 200000 lines.</p> <p>What can be done to speed this up?</p> <p>I implemented a real ViewModel per HighCore's suggestion. This is marginally faster, but it is still taking 5-6 seconds to go threw all the lines of the ObservableCollection</p> <pre><code>ICollectionView view = CollectionViewSource.GetDefaultView(this.LogView.ItemsSource); LogViewModel lvm = (LogViewModel)this.DataContext; view.Filter = o =&gt; { LogLine line = o as LogLine; if (line == null || !line.Message.Contains(lvm.FilterText)) { return false; } switch (line.LogLevel) { case LogViewModel.LogLevel.Trace: return lvm.Trace; case LogViewModel.LogLevel.Debug: return lvm.Debug; case LogViewModel.LogLevel.Info: return lvm.Info; case LogViewModel.LogLevel.Warn: return lvm.Warn; case LogViewModel.LogLevel.Error: return lvm.Error; default: return false; } }; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKevinA
    1. USKevinA
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMore efficient log filter
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMore efficient log filter
      1. USKevinA
      1. VTFavorite
    1. COJust an aside comment: the first 7 lines of your code are a horrible way to obtain data from the UI. you'd better create a proper ViewModel to hold that data.
      singulars
      1. POMore efficient log filter
      1. USFederico Berasategui
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload