[
https://issues.apache.org/jira/browse/OLIO-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706084#action_12706084
]
Shanti Subramanyam commented on OLIO-92:
----------------------------------------
We do back the db up and restore it before a run. But it would be nice to not
have to do this for every single test run. In the good old days when I ran
TPC-C, we would do a few runs, then restore the db. When it came time to get
the final results to be published, we would restore for every run. I'm looking
at a similar model here.
> Reloading the db in between runs should not be required
> -------------------------------------------------------
>
> Key: OLIO-92
> URL: https://issues.apache.org/jira/browse/OLIO-92
> Project: Olio
> Issue Type: Improvement
> Components: php-app
> Affects Versions: 0.1
> Reporter: Shanti Subramanyam
> Assignee: Shanti Subramanyam
>
> Currently, the Olio/PHP app and driver are structured such that after every
> run, the DB needs to be restored. Although this is easy enough to do for
> small loads, as we scale Olio to higher and higher levels, this becomes a
> time-consuming task. Note that this problem does not exist with the rails app
> as it uses MySQL Auto-id's for primary keys. You can load the db once and do
> multiple runs. The PHP app needs to adapt this same schema/method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
