Project

General

Profile

Actions
Copy link

Feature #6332

open

Improve searching with caching and JavaScript

Added by Jan Mach over 4 years ago. Updated over 1 year ago.

Status:
Feedback
Priority:
Normal
Assignee:
Jakub Maloštik
Category:
Development - GUI
Target version:
Future
Start date:
07/08/2020
Due date:
07/08/2020 (over 4 years late)
% Done:

0%

Estimated time:
To be discussed:
No

Description

This task originally comes from #6308. We left timeline calculations in stable state, but there are following possible improvements:

  • Use result caching.
  • Use JavaScript to dynamically calculate and load statistics in tabs on demand, so that the user does not have to wait.

These techniques could be used also elsewhere to improve usability and response time.

Related issues

Related to Mentat - Feature #6308: Reimplement timeline calculations on databaseClosedJan Mach04/09/2020

Actions
Has duplicate Mentat - Feature #6310: Implement result cachingClosed07/08/202007/08/2020

Actions
Follows Mentat - Feature #6413: Autarkic DB queries for timelineClosedJakub Maloštik07/07/2020

Actions
Actions
Copy link
 #1

Updated by Jan Mach over 4 years ago

  • Related to Feature #6308: Reimplement timeline calculations on database added
Actions
Copy link
 #2

Updated by Pavel Kácha over 4 years ago

  • Target version changed from 2.8 to Backlog
Actions
Copy link
 #3

Updated by Radko Krkoš over 4 years ago

  • Due date set to 07/08/2020
  • Start date changed from 05/19/2020 to 07/08/2020
  • Follows Feature #6413: Autarkic DB queries for timeline added
Actions
Copy link
 #4

Updated by Pavel Kácha almost 4 years ago

  • Assignee deleted (Jan Mach)
Actions
Copy link
 #5

Updated by Rajmund Hruška almost 2 years ago

  • Status changed from New to Resolved
  • Assignee set to Jakub Maloštik
  • Target version changed from Backlog to 2.11
Actions
Copy link
 #6

Updated by Rajmund Hruška almost 2 years ago

  • Status changed from Resolved to In Review

Deployed on mentat-alt.

Actions
Copy link
 #7

Updated by Rajmund Hruška almost 2 years ago

The ' #target types ' tab says No Data Available. I am not sure if that is related to this issue.

Actions
Copy link
 #8

Updated by Jakub Maloštik almost 2 years ago

Rajmund Hruska wrote in #note-7:

The ' #target types ' tab says No Data Available. I am not sure if that is related to this issue.

Yes, that tab wasn't there before, for some reason it appeared after my changes. The No Data Available is because most events don't include data for the `target_type` column. If a sufficiently large time window is selected and at least one event with this field is found, the data can be plotted. I'll figure out why the tab has appeared, and fix it.

Actions
Copy link
 #9

Updated by Rajmund Hruška over 1 year ago

Jakub Maloštik, if I understand your code correctly, we don't have the caching yet, do we?

Actions
Copy link
 #10

Updated by Rajmund Hruška over 1 year ago

  • Status changed from In Review to Feedback
Actions
Copy link
 #11

Updated by Jakub Maloštik over 1 year ago

Rajmund Hruška wrote in #note-9:

Jakub Maloštik, if I understand your code correctly, we don't have the caching yet, do we?

The plan is to have a backend cache, however right now there is javascript code ensuring frontend caching, which is to be removed after the backend caching is implemented.

Actions
Copy link
 #12

Updated by Rajmund Hruška over 1 year ago

  • Target version changed from 2.11 to Future
Actions
Copy link
 #13

Updated by Pavel Kácha 8 months ago

Actions
Copy link

Also available in: Atom PDF