timeShift Function doesn't graph all data when used inside sum() with wildcards

Bug #676395 reported by Nicholas Leskiw
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fix Released

Bug Description

if using wildcards and timeShift() inside a sum()

for example:

two problems occur:
1. Only the first match to the wildcard is summed to itself (so if there's 42 metrics, you'll get a graph of the first metric with a scale of 42).
2. As more metrics match, the function takes exponentially more time to complete.

With 42 metrics, it takes nearly a minute to draw the graph (incorrectly).

A quick fix is to use timeShift() outside the sum(). Either this needs to be fixed so it works properly or an error should be thrown preventing a huge CPU drain and incorrect graphs being drawn.

chrismd (chrismd)
Changed in graphite:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → chrismd (chrismd)
chrismd (chrismd)
Changed in graphite:
status: Confirmed → Fix Committed
chrismd (chrismd)
Changed in graphite:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.