In Python 2.7 and 2.6 (only ones I have tried), there is a bug in the turtle module's tracer() function, when applying it to multiple turtles using the same value.

When two turtles are defined (to draw simultaneously), and both turtles' tracers are set to the same number, one of the turtles does not end up following its tracer value. (It's a little hard to explain...look at/try the sample code)

The following script will recreate this glitch:
"
from turtle import *

t1 = Turtle()
t2 = Turtle()

for t in turtles():
    t.ht()
    t.speed(0)
    t.tracer(10)

t1.color("black")
t2.color("red")

for x in range(500):
    t1.forward(x)
    t2.forward(x)
    t1.left(144.5)
    t2.right(144.5)
"

To be more clear, in the sample code, the drawing animation of the red star-spiral is smooth, whereas the drawing animation of the black star-spiral is spasmodic.

2.6 is only open for security fixes.

In 3.x "The methods Turtle.tracer(), Turtle.window_width() and Turtle.window_height() have been eliminated. Methods with these names and functionality are now available only as methods of Screen."

So it seems that perhaps the fix was to make what you did impossible ;-). Hence, I am inclined to close this as 'out-of-date'. The deletion was not done in 2.7 for back-compatibility reasons.

Replacing "    t.tracer(10)" with "\nScreen().tracer(10)", the rosette is drawn in under a second (on my several-year-old machine). I cannot see any difference.