"Jeff Squyres \(jsquyres\)" <
jsquyres@...>
> One way to do this would be to define a perfbase experiment to be the
> result of a single test from the Intel test suite (for example). We
> could then submit to perfbase after each individual test executable (or
> be a bit more efficient and submit "a bunch" of them at once). But this
> will lead to a table explosion in the back-end database -- in the worst
> case where we submit one result at a time, each result will be a
> perfbase run, and therefore one table for will be created for each
> result. This will likely be so inefficient as to be prohibitive.
Sorry for the late reply.
The current version of perfbase does no longer create a new table for
each run, but only a new index. Indexes are cheap, but queries might
become somewhat slower if a large list of run indexes has to be
processed. Note that this really reads *might*, as I don't know how well
PostgreSQL handles/optimizes such SQL constructs.
> What we really want to be able to do is have a lot of test results
> submitted incrementally over time but not lead to a table explosion.
> Perhaps something like this scenario:
>
> me: "hey perfbase, please create an empty run for me and give me back an
> identifier for it"
> perfbase: "sure thing -- you now have run X"
> <time passes>
> me: "hey perfbase, here's a bunch of results, please put them in run X"
> <more time passes>
> me: "hey perfbase, here's a bunch of results, please put them in run X"
>
> ...and so on.
>
> Is something like this possible? Or, if not, do you have any
> suggestions about how we can submit partial results to perfbase without
> being horribly inefficient in the back-end database?
It's an important characteristic of perfbase that runs can not be
modified once they have been created. Thus, the thing you thought of
won't be possible.
However, it is possible to create a single run from an unlimited number
of input files by using the "--join" option for the input command. I
guess that's the way to go. Additionally, if you can not avoid to create
multiple perfbase runs for a single test suite run, you should group
these run via a dedicated parameter value, or use the synopsis for this.
Joachim
--
Joachim Worringen, Software Architect, Dolphin Interconnect Solutions
phone ++49/(0)228/324 08 17 -
http://www.dolphinics.com---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...
