Closed (fixed)
Project:
Drupal.org infrastructure
Component:
Other
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Jan 2009 at 17:34 UTC
Updated:
3 Jan 2014 at 00:07 UTC
Jump to comment: Most recent
Test and compare tracker2, a views based tracker and Drupal 6 tracker in terms of performance for the upgrade drupal.org. We keep rolling with Tracker 2 since it was required for the Drupal 5 site, but how much of a performance improvement does it help us gain? Is the Drupal 6 tracker became any better. Should we keep using the custom tracker2 module?
Comments
Comment #1
moshe weitzman commentedI am pretty certain that the D6 tracker improvements are not nearly what tracker2 does. Tracker2 is still required.
Comment #2
gábor hojtsyWhy are we not putting tracker 2 into the limelight then? Why is it not replacing core tracker still? (It says it has experimental PostgreSQL support even). Why do we ship with a slow module when we have a (said to be clearly) better replacement?
Comment #3
damien tournoud commented@Gábor: let's test and demonstrate then, but I'm with Moshe: the result makes little doubt.
By the way: any test of performance will need to benchmark concurrent insertions and selects. On a seldom written database, MySQL query cache can help the slow tracker query a lot.
Comment #4
catchBecause the issue hasn't had very much attention recently: #105639: Tracker performance improvements - although seeing this reminded me to re-roll the patch.
And possibly because if materialized views makes it into core, then the indexing stuff in tracker2 could be passed off to that.
Comment #5
catchI've re-rolled the patch in that issue and run benchmarks on a stock D7 site with 5,000 nodes - there's been no significant changes between Drupal 6 and 7 in tracker module. While that's a small amount of data, I'd expect the disparity to only get more extreme with more content.
Comment #6
gábor hojtsyAll right, seen the benchmark, hear the comments. Looks like there is nothing to debate here, tracker2 is clearly better for drupal.org at this point. It would be best to try and improve on the core tracker in later versions of Drupal 6, if that would help us eliminate this contrib module later. :) But the goal of this issue is accomplished, we will use tracker2 for now.