Dear Calle
Thank you for your information. 127 GB Databases size is including
analytics. Yes disks are in RAID 5.
Do you have tracker on that instances? Possible to share tomcat and DB
tuning parameters?
Please suggest.
Regards
Hannan
On Tue, May 1, 2018 at 3:36 AM, Calle Hedberg
wrote:
> H
Hannan,
Out of interest: how do you measure your DB size? "127GB" does not really
say much - is it with or without analytics tables etc. Are you just using
pg_database_size?
I just ran that on my local instance of the South African "national" HMIS
instance - it is 202 GB (NOTE: that includes anal
Thanks Bob.
I remembered that. 1st step I takes was upgrade postgres to 9.6 and tuning
parameters which reduced time from 58 to 13 hour. And after that I
removed/update the data types of the aggregated data set what was
changed/amended that reduce the time to 8 hour.
1. this time it is gradually
Hi Hannan
I recall you had a similar request which I responded to back in Jan 11.
Maybe worth re-reading that thread as some of it seems still to be
relevant. In particular:
1. The first question, as always, is has this suddenly happened or has
something recently changed? Back then there had b
Dear Experts
I am drawing your attention to one problem and need your kind attention. In
one of our DHIS2 instances, 'Central Server' analytics generation taking
too much time 12 h, 22 m, 34 s. DB size is 127 GB and have aggregated and
trackers as. During analytics run-time the processor utilizat
5 matches
Mail list logo