double sending Talos results to two graph servers.

[alice nodelman]

I've covered the details of this in my recent blog post:

http://alice.nodelman.net/blog/post/double-sending-talos-results-to-new-improved-graph-server/

The main change is going to be to the format of the results found in the
Talos columns on the waterfall. Along with the standard links to
graphs.mozilla.org there will be second set of links provided to
graphs-new.mozilla.org.

I think that this is going to be a great way to move towards using the
new graph server without disrupting any of our building and testing
infrastructure, there should be no need for a downtime and even if bugs
are found in the new graph server set up the same data will always be
available in the 'classic' graph server links.

Once we've successfully had data reporting to both old and new for a
couple of weeks, or up to a month, we'll consider moving towards only
sending data to the new graph server and migrating any bits and pieces
of data from the old db that we are interested in salvaging.

I'd be happy to field any questions/comments.

Thanks,
alice.

[Mark Banner]

On 25/2/09 22:25, alice nodelman wrote:
> Once we've successfully had data reporting to both old and new for a
> couple of weeks, or up to a month, we'll consider moving towards only
> sending data to the new graph server and migrating any bits and pieces
> of data from the old db that we are interested in salvaging.
>
> I'd be happy to field any questions/comments.

What are the plans for migrating the leak and bloat numbers across to
the new graph server?

At the moment Thunderbird has numbers that aren't valid displayed
anywhere. Whilst its not too much of an issue for leak and bloat, I'd
like to know what the plan is as to when we'll be able to get them
running again (and what we'll have to track/port to get to that stage).

Thanks
Mark.

[alice nodelman]

Leak/bloat numbers will continue to be sent exclusively to
graphs.mozilla.org. I have the code written which can send the same
data which is generated by Firefox builders to graphs-new.mozilla.org,
but will not be doing the switch over till we are confident that the new
server is working appropriately.

If Tbird results are currently being sent to graphs.m.o., they should
continue to do so. We aren't doing any harsh deadlines here - once the
Firefox leak/bloat numbers are being sent to graphs-new.mozilla.org we
can work to get all other projects reporting in a similar fashion.

alice.