[
https://issues.apache.org/jira/browse/OLIO-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705775#action_12705775
]
Matt Ingenthron commented on OLIO-92:
-------------------------------------
Large installations of MySQL/InnoDB do see fragmentation of the database files
after much use. This could also affect results if you have many iterations on
the same database files. Perhaps it's best to somehow back them up after the
initial population rather than re-create. Keeping the same files around
between multiple runs is probably not advisable.
> 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.
