# CommCare HQ Slowness **URL:** \ **Category:** Users\ **Created:** [August 19, 2013, 12:53pm UTC](https://forum.dimagi.com/t/commcare-hq-slowness/1487 "2013-08-19T12:53:44Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![czue](https://dimagi.b-cdn.net/user_avatar/forum.dimagi.com/czue/32/493_2.png) [@czue](https://forum.dimagi.com/u/czue)\ **Post date:** [August 19, 2013, 12:53pm UTC](https://forum.dimagi.com/t/commcare-hq-slowness/1487/1 "2013-08-19T12:53:44Z")
Hi all, We are aware of extreme slowness on CommCare HQ. Our database server is experiencing very heavy load and we are working urgently with our provider to understand and address the issue. Please bear with us as we work to resolve this as fast as we can. thanks, the CommCare HQ team ---
**Author:** ![james\_beard](https://dimagi.b-cdn.net/letter_avatar_proxy/v4/letter/j/8e8cbc/32.png) [@james\_beard](https://forum.dimagi.com/u/james_beard)\ **Post date:** [August 19, 2013, 1:42pm UTC](https://forum.dimagi.com/t/commcare-hq-slowness/1487/2 "2013-08-19T13:42:29Z")
Is that why I'm getting repeated Whoops, that didn't go through. Reload the page and click Make New Version to try again. when trying to build my application? Thanks. > **···** > > On Monday, August 19, 2013 12:53:44 PM UTC, Cory Zue wrote: \> \> Hi all, \> \> We are aware of extreme slowness on CommCare HQ. Our database server is \> experiencing very heavy load and we are working urgently with our provider \> to understand and address the issue. Please bear with us as we work to \> resolve this as fast as we can. \> \> thanks, \> the CommCare HQ team \> ---
**Author:** ![czue](https://dimagi.b-cdn.net/user_avatar/forum.dimagi.com/czue/32/493_2.png) [@czue](https://forum.dimagi.com/u/czue)\ **Post date:** [August 19, 2013, 11:01pm UTC](https://forum.dimagi.com/t/commcare-hq-slowness/1487/3 "2013-08-19T23:01:11Z")
Hi all, Just to follow up on the original thread, we are still working with the database provider to resolve these issues. We anticipate that CommCare HQ will continue to be much slower than usual for the next 12-24 hours until we are both able to do a more thorough audit of the problem and begin working towards a resolution. In the meantime there is no need to report additional slowness via this mailing list or our issue reporting systems. We will provide an additional update as soon as we know more information. In the meantime unless it is absolutely critical to your workflow we kindly ask that you refrain from doing heavy, data intensive operations. These include _all form, case or metadata exports_, _viewing reports over large time ranges_, bulk case reassignment, deleting users, bulk imports of users, cases, or fixtures. This will allow the system to be more responsive to the most crucial workflows like front line worker syncs and submissions. We are doing everything in our power to restore the normal functionality of the site, and please bear with us and be patient through that process. thanks, HQ team > **···** > > On Mon, Aug 19, 2013 at 8:53 AM, Cory Zue wrote: > > > Hi all, > > > > We are aware of extreme slowness on CommCare HQ. Our database server is > > experiencing very heavy load and we are working urgently with our provider > > to understand and address the issue. Please bear with us as we work to > > resolve this as fast as we can. > > > > thanks, > > the CommCare HQ team ---
**Author:** ![dannyroberts](https://dimagi.b-cdn.net/letter_avatar_proxy/v4/letter/d/94ad74/32.png) [@dannyroberts](https://forum.dimagi.com/u/dannyroberts)\ **Post date:** [August 19, 2013, 1:57pm UTC](https://forum.dimagi.com/t/commcare-hq-slowness/1487/4 "2013-08-19T13:57:48Z")
Hi James, Yes, that is very likely related, unfortunately. If it persists after this problem is under control, please let us know. Best, Danny > **···** > > On Mon, Aug 19, 2013 at 9:42 AM, james beard wrote: > > > Is that why I'm getting repeated Whoops, that didn't go through. Reload > > the page and click Make New Version to try again. when trying to build my > > application? > > > > Thanks. > > > > On Monday, August 19, 2013 12:53:44 PM UTC, Cory Zue wrote: > > > > > Hi all, > > > > > > We are aware of extreme slowness on CommCare HQ. Our database server is > > > experiencing very heavy load and we are working urgently with our provider > > > to understand and address the issue. Please bear with us as we work to > > > resolve this as fast as we can. > > > > > > thanks, > > > the CommCare HQ team > > > > -- > > You received this message because you are subscribed to the Google Groups > > "commcare-users" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [commcare-users+unsubscribe@googlegroups.com](mailto:commcare-users+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![czue](https://dimagi.b-cdn.net/user_avatar/forum.dimagi.com/czue/32/493_2.png) [@czue](https://forum.dimagi.com/u/czue)\ **Post date:** [August 20, 2013, 11:38pm UTC](https://forum.dimagi.com/t/commcare-hq-slowness/1487/5 "2013-08-20T23:38:32Z")
Hi all, Another follow up - we are still gathering information and working on this. We have taken some temporary precautions to make things more load tolerant and CommCare HQ appears to be functioning normally (perhaps a bit slower than usual) although we are not 100% sure that it will continue to be performant during peak load hours (which typically occur from 2am - 10am EDT). Many of the fixes that need to be made are quite complicated, so we will be continuing to be monitoring this closely and incrementally making changes to restore performance to the site over the course of the next few days (possibly weeks). In the meantime, you can use CommCare HQ normally and hopefully the changes we have made so far will hold up. thanks for being patient, Cory > **···** > > On Mon, Aug 19, 2013 at 7:01 PM, Cory Zue wrote: > > > Hi all, > > > > Just to follow up on the original thread, we are still working with the > > database provider to resolve these issues. We anticipate that CommCare HQ > > will continue to be much slower than usual for the next 12-24 hours until > > we are both able to do a more thorough audit of the problem and begin > > working towards a resolution. In the meantime there is no need to report > > additional slowness via this mailing list or our issue reporting systems. > > We will provide an additional update as soon as we know more information. > > > > In the meantime unless it is absolutely critical to your workflow we > > kindly ask that you refrain from doing heavy, data intensive operations. > > These include _all form, case or metadata exports_, _viewing reports over > > large time ranges_, bulk case reassignment, deleting users, bulk imports > > of users, cases, or fixtures. This will allow the system to be more > > responsive to the most crucial workflows like front line worker syncs and > > submissions. > > > > We are doing everything in our power to restore the normal functionality > > of the site, and please bear with us and be patient through that process. > > > > thanks, > > HQ team > > > > On Mon, Aug 19, 2013 at 8:53 AM, Cory Zue [czue@dimagi.com](mailto:czue@dimagi.com) wrote: > > > > > Hi all, > > > > > > We are aware of extreme slowness on CommCare HQ. Our database server is > > > experiencing very heavy load and we are working urgently with our provider > > > to understand and address the issue. Please bear with us as we work to > > > resolve this as fast as we can. > > > > > > thanks, > > > the CommCare HQ team ---
**Author:** ![czue](https://dimagi.b-cdn.net/user_avatar/forum.dimagi.com/czue/32/493_2.png) [@czue](https://forum.dimagi.com/u/czue)\ **Post date:** [August 23, 2013, 2:13am UTC](https://forum.dimagi.com/t/commcare-hq-slowness/1487/6 "2013-08-23T02:13:31Z")
Hi everyone, Just a quick update from our side on this. Our database provider is still working to upgrade our machines and restore performance to CommCare HQ. We expect the site will continue to be significantly slower than normal for the next 12 hours while this is happening. We should have another update at that time. Cory > **···** > > On Tue, Aug 20, 2013 at 7:38 PM, Cory Zue wrote: > > > Hi all, > > > > Another follow up - we are still gathering information and working on > > this. We have taken some temporary precautions to make things more load > > tolerant and CommCare HQ appears to be functioning normally (perhaps a bit > > slower than usual) although we are not 100% sure that it will continue to > > be performant during peak load hours (which typically occur from 2am - 10am > > EDT). > > > > Many of the fixes that need to be made are quite complicated, so we will > > be continuing to be monitoring this closely and incrementally making > > changes to restore performance to the site over the course of the next few > > days (possibly weeks). > > > > In the meantime, you can use CommCare HQ normally and hopefully the > > changes we have made so far will hold up. > > > > thanks for being patient, > > Cory > > > > On Mon, Aug 19, 2013 at 7:01 PM, Cory Zue [czue@dimagi.com](mailto:czue@dimagi.com) wrote: > > > > > Hi all, > > > > > > Just to follow up on the original thread, we are still working with the > > > database provider to resolve these issues. We anticipate that CommCare HQ > > > will continue to be much slower than usual for the next 12-24 hours until > > > we are both able to do a more thorough audit of the problem and begin > > > working towards a resolution. In the meantime there is no need to report > > > additional slowness via this mailing list or our issue reporting systems. > > > We will provide an additional update as soon as we know more information. > > > > > > In the meantime unless it is absolutely critical to your workflow we > > > kindly ask that you refrain from doing heavy, data intensive operations. > > > These include _all form, case or metadata exports_, _viewing reports > > > over large time ranges_, bulk case reassignment, deleting users, bulk > > > imports of users, cases, or fixtures. This will allow the system to be more > > > responsive to the most crucial workflows like front line worker syncs and > > > submissions. > > > > > > We are doing everything in our power to restore the normal functionality > > > of the site, and please bear with us and be patient through that process. > > > > > > thanks, > > > HQ team > > > > > > On Mon, Aug 19, 2013 at 8:53 AM, Cory Zue [czue@dimagi.com](mailto:czue@dimagi.com) wrote: > > > > > > > Hi all, > > > > > > > > We are aware of extreme slowness on CommCare HQ. Our database server is > > > > experiencing very heavy load and we are working urgently with our provider > > > > to understand and address the issue. Please bear with us as we work to > > > > resolve this as fast as we can. > > > > > > > > thanks, > > > > the CommCare HQ team