Baselines

[Steffen Schwigon]

Hi!

Maybe I'm wearing my blinders: how can I define baselines?

Thanks.

Kind regards,
Steffen
--
Steffen Schwigon <s...@renormalist.net>

[Miquel Torres]

In the "Further customization" section of the README, scroll down to
the "Defaults" subsection.

The DEF_BASELINE option in settings.py defines which exe/rev should be default.

In addition, Codespeed will automatically add as baseline options any
tagged revisions (Django admin->revisions->select one->add tag)

2011/12/2 Steffen Schwigon <s...@renormalist.net>:

[Steffen Schwigon]

[Sorry for the late reply.]

Miquel Torres <tob...@googlemail.com> writes:
> In the "Further customization" section of the README, scroll down to
> the "Defaults" subsection.
>
> The DEF_BASELINE option in settings.py defines which exe/rev should be default.
>
> In addition, Codespeed will automatically add as baseline options any
> tagged revisions (Django admin->revisions->select one->add tag)

Somehow I don't get it.

None of my experiments get me any baseline drawn.

What am I expected to fill in as “tag” in admin/revisions…?

At least these admin settings get the select-box filled with all
executables but I don't understand what the tag then is. A git tag? If I
try a git tag it has no effect.

On the other front, the DEF_BASELINE in settings.py has no effect
whatsoever although that seemed to be the right thing. I tried a line
like this:

DEF_BASELINE = {'executable': 'perl-5.10-thread-64bit', 'revision': 'c04726a784'}

with revision being long SHA1, short SHA1, internal ID, whatever, no
effect.

Any more hints I should try?

I run a “quite latest” version from git master.

Thanks.

Kind regards,
Steffen

>
>
>
> 2011/12/2 Steffen Schwigon <s...@renormalist.net>:
>> Hi!
>>
>> Maybe I'm wearing my blinders: how can I define baselines?
>>
>> Thanks.
>>
>> Kind regards,
>> Steffen
>> --
>> Steffen Schwigon <s...@renormalist.net>
>

--
Steffen Schwigon <s...@renormalist.net>

[Miquel Torres]

Hi,

a tag is any name you want to give a revision. Ideally it is a version
tag, corresponding to a git tag, buy it is codespeed specific though.

Regarding the setting, it should be the whole SHA1 string, or whatever
you used as commitid to save the revision.

But first things first: You need to get the baseline menu filled out.
You will only get that by asigning a tag for a revision. Doesn't that
work for you? You really entered some text in the tag field of a
revision of one of your projects and it doesn't show up in the
timeline baseline menu? That would be a bug.

2012/1/1 Steffen Schwigon <s...@renormalist.net>:

[Steffen Schwigon]

Miquel Torres <tob...@googlemail.com> writes:
> Hi,
>
> a tag is any name you want to give a revision. Ideally it is a version
> tag, corresponding to a git tag, buy it is codespeed specific though.
>
> Regarding the setting, it should be the whole SHA1 string, or whatever
> you used as commitid to save the revision.

I see, ok.

> But first things first: You need to get the baseline menu filled out.
> You will only get that by asigning a tag for a revision.

Ok, yes, we try step by step.

- I assigned a tag “baseline” to one particular commit.
This gets me the select-box filled, see

http://speed.perlformance.net/timeline/#/?exe=14,23&base=23+80&ben=grid&env=4&revs=50&equid=off

- Funny, for the first time ever, I see a small horizontal line here:

http://speed.perlformance.net/timeline/#/?exe=14,23&base=23+80&ben=%28F%29DPath.dpath&env=4&revs=50&equid=off

after chosing “Baseline: perl-5.8-thread64bit baseline”.

Is that little straight line on the right the baseline?
I had expected it over the whole width from left to right,
especially when adding other executables.

So far for now. At least it looks like progress, just not sure it's
already The Right Thing.

Kind regards,
Steffen

--
Steffen Schwigon <s...@renormalist.net>

[Steffen Schwigon]

Steffen Schwigon <s...@renormalist.net> writes:
> - Funny, for the first time ever, I see a small horizontal line here:
>
> http://speed.perlformance.net/timeline/#/?exe=14,23&base=23+80&ben=%28F%29DPath.dpath&env=4&revs=50&equid=off
>
> after chosing “Baseline: perl-5.8-thread64bit baseline”.
>
> Is that little straight line on the right the baseline?
> I had expected it over the whole width from left to right,
> especially when adding other executables.

Aha, it might be related to the nonorthodox way I assign my “exes”. My
executables are versioned and therefore in several ranges of the overall
timeline.

The line moves if I chose only 10 last results and enable other
exes. Maybe its left/right/width is evaluated from drawn results instead
of complete left to right?

[Miquel Torres]

Correct. That is an artifact due to the jqplot implementation. It
should be possible to fix it.

2012/1/3 Steffen Schwigon <s...@renormalist.net>:

[Steffen Schwigon]

Hi!

If you give me a hint where to search (files, subdir, functions) I try
to help fix, I'm just short of time to understand codespeed from the
beginning to find the spot.

Kind regards,
Steffen

--
Steffen Schwigon <s...@renormalist.net>

[Miquel Torres]

Sorry for not being very responsive, in the last weeks I didn't have
much time to work on the different Codespeed issues that have cropped
up.

So now I took the time to document what the exact baseline problem is:
https://github.com/tobami/codespeed/issues/111

Give it a try!

2012/1/8 Steffen Schwigon <s...@renormalist.net>: