It would be intersting to knows which kind of backup you are usinmg: could
you send us the commands/scripts and generally speaking the backup
procedure you are using?
Best
"Amy Bensinger
(Contractor)"
<[EMAIL PROTECTED] To
enfoundation.org> Biren Patnik/Ireland/[EMAIL PROTECTED],
Sent by: "Aliya Walji"
mifos-developer-b <[EMAIL PROTECTED]>
[EMAIL PROTECTED] cc
ceforge.net Van Mittal-Henkle
<[EMAIL PROTECTED]>, Developer
<[EMAIL PROTECTED]
02/01/2008 01:26 net>, Mifos Dev
PM <[EMAIL PROTECTED]>
Subject
Re: [Mifos-developer] Database
Please respond to Growth
Developer
<mifos-developer@
lists.sourceforge
.net>
I’m working on getting more information from Grameen Koota. The size of
the database backups each day are now 350 – 450 MB per day larger—the same
as in October. The database size currently is 48 GB. One month ago, it
was 43 GB
We are gathering the total database file size each day going forward.
Perhaps the problem can be fixed by changing how the backup is done?
One other note—I looked at the table list again. The CUSTOMER
table—although currently among the largest—is not going to see a lot of
size increases because GK is not adding new branches at this time.
As to your other questions, perhaps someone who knows the original design
decisions better can respond?
What was the maximum size allowed at design and implementation time for
Mifos DB?
Is 100MB a reasonable growth compared with your initial forecast or is it
too much?
Is it needed to scale the current DB?
Is that the abnormal growth due to application bug?
From: Biren Patnik [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 31, 2008 8:59 PM
To: Aliya Walji; Amy Bensinger (Contractor)
Cc: Mifos Dev; Van Mittal-Henkle; Developer; Beth Mazur
Subject: Database Growth
Hi Aliya,
Thanks for your email.
Just a brief summary on the issues related to the database growth problem:
We have been informed in the month of November 2007 from Grameen Koota that
they see an abnormal growth of 450 MB per day
As requested, some data were collected and sent to us few days ago by Aliya
and Amy (thanks to both of them).
A. We analyzed statically these data in the following ways:
We are convinced that only 6 table are contributing at least for 87% of the
total size.
We concentrate our analysis efforts on these tables and we extracted the
data for the week 13-19th Dec 2007,14-20th and 21-27th January 2008
The results are reported in the spreadsheet named comparison.xls
A.1 Findings from comparison.xls
We know that looking only 21 days is not enough, but we got some more
information that are quite different from the starting one.
As you can see in comparison.xls the daily grow seems no more than 50 MB
(quite different from the 450 MB initially communicated to us the week of
November 2007)
50 MB total data length growth per day can be realistic (100MB in total
considering all tables and indexes), but still far from 450 MB per day.
So far, some questions:
What was the maximum size allowed at design and implementation time for
Mifos DB?
Is 100MB a reasonable growth compared with your initial forecast or is it
too much?
Is it needed to scale the current DB?
Is that the abnormal growth due to application bug?
Clearly our analysis was done on data between 13th December 2007 to 28th
January 2008, while the abnormal growth was observered in October 2007:
These are some of the questions which needs to be addressed ..
Is there anything changed between October and December?
Does any system administrator/DBA make any changes to the database during
December?
Has this problem been fixed in the application by anyone during November
,December and January 08
If you still find 450mb database growth per day then what we found out from
the excel sheet is probably not correct?
========================================================================
B. One of our colleagues are defining two different scenarios to stress
MySql Mifos database re-produced on our machine.
The two scenarios are:
bulk entry,
loan account creating
We should be able to run the first stress tests hopefully late next week.
In order to analyze the results we need also to set up correctly our
environment
In order to set up correctly our test environment we need to know:
1. Hardware where the DB is running: Operating System, CPU, Memory, Disk
Size and their management and free space currently in Grameen Koota.
2. If other software is running on DB server along with MySql.
3. How many cuncurrent users are currently for Mifos database.
4. Volume of critical job activity (max size)
Thanks and Kind Regards
Biren Patnaik
Lead Software Developer
IBM Technology Campus
Damestown Industrial Park,Mulhuddart
Dublin 15
Internal Tel: 511211
External Tel : (+353) - 1 - 815-1211
Email: [EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
