User:Ondrej/Bugs/385245: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(New page: Bug 38245 History sidebar supports multiple views, for each query there is one query performed which reads all the data to be displ...)
 
No edit summary
Line 4: Line 4:


Testing conditions:
Testing conditions:
- No favicons
* No favicons (they seems to slow down display of the sidebar and should be solved separately).
- Three databases
* Loading time is just the time spent in the database engine.
 
* Three databases of various size:
{| border="1"
{| border="1"
! Database || Places || Visits  
! Database || Places || Visits  
Line 17: Line 17:
|}
|}


= Views =


= View by Site =
== View by Date and Site ==
=== Current Situation ===
=== Future Situation ===


== View by Site ==
=== Current Situation ===
=== Current Situation ===
Loads all places and their visits, does  
Loads all places and their visits, does  
=== Future Situation ===


== View by Date ==
=== Current Situation ===
Loads all places and all related visits to memory, processes the data in memory and creates groups by days.
{| border="1"
! Database || Loading Time || Records
|-
| Small ||align=right|88||align=right|15124
|-
| Mid ||align=right|589||align=right|76250
|-
| Bug ||align=right|3276||align=right|255363
|}
=== Future Situation ===
=== Future Situation ===


=== View by Last Visited ===


== View by Most Visited ==
=== Current Situation ===
Joins places with history, this could be avoided if the visit_count is only updated for proper visit_types (to be checked).
=== Future Situation ===
Requires incremental loading.
== View by Last Visited ==
=== Current Situation ===
Correct query, loads all the places and their last visit.
Correct query, loads all the places and their last visit.
=== Future Situation ===
Requires incremental loading.


=== View by Most Visited ===
= Incremental loading =
 
Joins with history, what would be useless in case when visit_count gets only increased for proper visit_types (I did not check).
 
== Future Situation ==

Revision as of 17:06, 19 December 2007

[38245]

History sidebar supports multiple views, for each query there is one query performed which reads all the data to be displayed on the view. The more data is in the database the longer it takes to display the sidebar.

Testing conditions:

  • No favicons (they seems to slow down display of the sidebar and should be solved separately).
  • Loading time is just the time spent in the database engine.
  • Three databases of various size:
Database Places Visits
Small 88 15124
Mid 589 76250
Bug 3276 255363

Views

View by Date and Site

Current Situation

Future Situation

View by Site

Current Situation

Loads all places and their visits, does

Future Situation

View by Date

Current Situation

Loads all places and all related visits to memory, processes the data in memory and creates groups by days.

Database Loading Time Records
Small 88 15124
Mid 589 76250
Bug 3276 255363

Future Situation

View by Most Visited

Current Situation

Joins places with history, this could be avoided if the visit_count is only updated for proper visit_types (to be checked).

Future Situation

Requires incremental loading.

View by Last Visited

Current Situation

Correct query, loads all the places and their last visit.

Future Situation

Requires incremental loading.

Incremental loading