<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Ashley,<br>
<br>
How do you envisage the passes and flag passes tables being used?
Usually one flag triggers a set of passes. Also why is order
needed in both flags_passes and passes?<br>
<br>
Cheers,<br>
James<br>
<br>
On 30/08/13 12:14, Ashley Whetter wrote:<br>
</div>
<blockquote
cite="mid:CAFECyJLLwqW5mkFHw570iherX68adEghcHP3g3PbCz-9NE17mA@mail.gmail.com"
type="cite">
<div dir="ltr">Hello again everyone,
<div><br>
</div>
<div>Thanks for everyone's feedback so far. As per James'
recommendation I've removed the raw_results table and put
results about a specific run in the runs table, and summary
data about a test in the test table.</div>
<div><br>
</div>
<div>Also, after a discussion with Kerstin about how useful the
database structure would be for the machine learning it was
realised that the database wouldn't be storing any information
about compiler passes.</div>
<div>Therefore the diagram has been changed so that flag sets
and feature vectors are associated with a pass instead of a
test. A test can also have multiple passes.</div>
<div><br>
</div>
<div>Here's the new diagram: <a moz-do-not-send="true"
href="http://mageec.org/wiki/File:Results_ERD_Proposal.png">http://mageec.org/wiki/File:Results_ERD_Proposal.png</a></div>
<div>I'll link to this page from now one so that it's easier to
see differences between different versions of the diagram.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Ashley</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 29 August 2013 10:50, Ashley Whetter
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:aw0455@my.bristol.ac.uk" target="_blank">aw0455@my.bristol.ac.uk</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Right you are. I've updated the diagram: <a
moz-do-not-send="true"
href="http://mageec.org/w/images/1/19/Results_ERD_Proposal.png"
target="_blank">http://mageec.org/w/images/1/19/Results_ERD_Proposal.png</a>
<div>I've also rename "time" to "timestamp" and "energy"
to "power".<span class="HOEnZb"><font color="#888888"><br>
<div><br>
</div>
<div>Ashley</div>
</font></span></div>
</div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 29 August 2013 10:35,
Munaaf Ghumran <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:mg0950.2010@my.bristol.ac.uk"
target="_blank">mg0950.2010@my.bristol.ac.uk</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I agree with James that the
flags_tests and run tables might need test_id as
shared foreign keys.
<div><br>
</div>
<div>Other than that, nothing I can see that
stands out, seems good!</div>
<div><br>
</div>
<div>Moon</div>
</div>
<div>
<div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 28 August 2013
19:08, James Pallister <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:James.Pallister@bristol.ac.uk"
target="_blank">James.Pallister@bristol.ac.uk</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi,
<div><br>
<br>
<blockquote type="cite">
<div>A test (and test id) refers
to a single combination of a
platform, compiler, benchmark,
and flag set.</div>
<div>A run (and run id) refers
to a single run of a test. A
test can have multiple runs.</div>
</blockquote>
</div>
In the ERD, do the flags_tests and
runs tables need test_id?
<div><br>
<br>
<blockquote type="cite">The
raw_results table is the
bottleneck. We record 200,000+
individual results for a single
run, so this table will get
really quickly.</blockquote>
</div>
I'm guessing this is the power trace
directly from the measurement board?
If so, the fields should be run_id,
timestamp and power.<br>
<br>
We may not want to store the entire
trace in the database - with
millions of measurements, the
database might get unmanagably large
- might be better if the raw_results
was just the time, energy, average
power, peak power, etc for that
specific run.
<div><br>
<br>
<blockquote type="cite">We could
split this out into a different
results table, but it's a
one-to-one relationship </blockquote>
</div>
The join between tests and runs
should be changed from one-to-many
in the diagram to one-to-one.<br>
<br>
<br>
Looks good from the energy
measurement side :)<span><font
color="#888888"><br>
<br>
<br>
James</font></span>
<div>
<div><br>
<br>
On 28/08/13 18:24, Simon Hollis
wrote:<br>
</div>
</div>
</div>
<div>
<div>
<blockquote type="cite">
<div>Hi Ashley,<br>
<br>
Thanks very much for starting
this discussion. This is a
really good starting point.<br>
<br>
What I would like is that if
everybody who has an interest
in the structure of this
database can provide their
feedback on the structure that
Ashley has proposed and see if
it will work for their
anticipated needs.<br>
<br>
As I see it there are at least
three interests we need to
support: Energy Measurement;
the MAGEEC framework; ML.<br>
<br>
Perhaps all sides could
outline the suitability of the
proposed structure for their
needs?<br>
<br>
P.S. for Magicians: If you
received this message, but not
Ashley's original one, it is
because you are not yet signed
up for the external <a
moz-do-not-send="true"
href="mailto:mageec@mageec.org"
target="_blank">mageec@mageec.org</a>
mailing list. Please do so!<br>
<br>
<br>
On 28/08/13 17:21, Ashley
Whetter wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hey everyone,
<div><br>
</div>
<div>At the last meeting we
looked at the ER diagram (<a
moz-do-not-send="true"
href="http://mageec.org/wiki/Database"
target="_blank">http://mageec.org/wiki/Database</a>) for
the database that would
store the results that
would be recorded by the
test framework and used by
the plugin.</div>
<div><br>
</div>
<div>I've taken some of the
comments made at the
meeting and made a more
detailed ER diagram to
discuss. (<a
moz-do-not-send="true"
href="http://mageec.org/w/images/1/19/Results_ERD_Proposal.png"
target="_blank">http://mageec.org/w/images/1/19/Results_ERD_Proposal.png</a>)</div>
<div><br>
</div>
<div>A test (and test id)
refers to a single
combination of a platform,
compiler, benchmark, and
flag set.</div>
<div>A run (and run id)
refers to a single run of
a test. A test can have
multiple runs.</div>
<div><br>
</div>
<div>Currently the flag
table is only really
storing a flag name (eg
"-fgcse", "-fno-gcse",
etc). I've kept this as a
separate table, though,
because eventually we'll
want to start storing
values for flags that
aren't just on or off. We
could add this value field
now, keep the table as is
for now, or get rid of
flag_id all together and
just use the flag name in
flags_tests instead.</div>
<div><br>
</div>
<div>I've put summary data
in the runs table. We
could split this out into
a different results table,
but it's a one-to-one
relationship it would add
an unnecessary overhead of
joining the runs and
results table when we want
to search it. This isn't
such a problem if we
search for results by
run_id though.</div>
<div><br>
</div>
<div>The raw_results table
is the bottleneck. We
record 200,000+ individual
results for a single run,
so this table will get
really quickly.</div>
<div><br>
</div>
<div><br>
</div>
<div>Ashley</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
mageec mailing list
<a moz-do-not-send="true" href="mailto:mageec@mageec.org" target="_blank">mageec@mageec.org</a>
<a moz-do-not-send="true" href="http://mageec.org/cgi-bin/mailman/listinfo/mageec" target="_blank">http://mageec.org/cgi-bin/mailman/listinfo/mageec</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
mageec mailing list<br>
<a moz-do-not-send="true"
href="mailto:mageec@mageec.org"
target="_blank">mageec@mageec.org</a><br>
<a moz-do-not-send="true"
href="http://mageec.org/cgi-bin/mailman/listinfo/mageec"
target="_blank">http://mageec.org/cgi-bin/mailman/listinfo/mageec</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mageec mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mageec@mageec.org">mageec@mageec.org</a>
<a class="moz-txt-link-freetext" href="http://mageec.org/cgi-bin/mailman/listinfo/mageec">http://mageec.org/cgi-bin/mailman/listinfo/mageec</a>
</pre>
</blockquote>
<br>
</body>
</html>