[
http://mifosforge.jira.com/browse/MIFOSBI-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kay Chau updated MIFOSBI-293:
-----------------------------
Status: Ready to Ship / Verified (was: Ready for Showcase)
> Update ETL to perform better when innodb_flush_log_at_trx_commit=1 (full acid
> behaviour)
> ----------------------------------------------------------------------------------------
>
> Key: MIFOSBI-293
> URL: http://mifosforge.jira.com/browse/MIFOSBI-293
> Project: mifos business intelligence
> Issue Type: Improvement
> Affects Versions: Mifos BI 1.1 - Iteration 1
> Reporter: johnwoodlock
> Assignee: johnwoodlock
> Fix For: Mifos BI 1.2 - Iteration 3
>
>
> Testing to-date on ETL has been with mysql configuration
> innodb_flush_log_at_trx_commit=0
> This config 'optimises' database writes but leaves the door open to losing
> just over a seconds worth of transactions. In the event of a mysql or OS
> crash, it depends on the recovery strategy whether this matters or not.
> This change improves transaction usage and batch size to minimise the 'gap'
> between a config setting of 0 and 1 so that people who feel they need a
> setting of 1 are not overly penalised.
> In a test example :
> ETL with config set to 0 121 mins
> same ETL with config set to 1 133 mins.
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
