Home → Problems →

Reports so slow I would call them broken

• Edit

bhspencer

20 Oct, 2012 01:08 AM

Hi

I've been using tender app for moneydance.com fro a few years now and in the last year I have noticed that the reports have become increasing slow to generate. Very occasionally the reports are working fine, half the time it takes multiple mins often it seems the reports never generate.

Could someone take a look at this please.

Ben Spencer

1. 1 Posted by Nicole on 21 Oct, 2012 03:49 PM

   

   Ben -

   Is it any specific report or just all reports across the board load slowly for you? Let us know and we'll take a look.

   Thanks,
   Nicole

   • Edit

2. 2 Posted by bhspencer on 22 Oct, 2012 04:03 PM

   

   Nicole

   I would say the "Staff responses" report is the one that most often takes forever or fails completely.

   Ben

   • Edit

3. 3 Posted by Amanda on 22 Oct, 2012 06:48 PM

   

   Ben,

   Is it possible for you to try the link in another browser and see if that produces better results?

   • Edit

4. 4 Posted by bhspencer on 22 Oct, 2012 08:06 PM

   

   Amanda,

   I tried it in Firefox, Chrome and Safari none produce the report in over a min of waiting.

   I fired up the Chrome javascript console and took a look at the network output. A screenshot is attached.

   Looking at the http response to GET supporter_history.json is see that your server sent back the "We're sorry, but something went wrong" message.

   Ben

   • Screen_Shot_2012-10-22_at_4.02.56_PM.png 448 KB
   • Edit

5. 5 Posted by Julien on 22 Oct, 2012 08:43 PM

   

   Hey Ben,

   I took a look at your site and all reports where pretty snappy. Next time you access one and get a long response time, or no response at all, can you write back immediatly and let me know the time and URL? I should be able to find it in our logs and get more info then.

   Thanks.

   • Edit

6. 6 Posted by bhspencer on 22 Oct, 2012 11:33 PM

   

   Just tried the repot again and got no results.

   Here is the screenshot

   • Screen_Shot_2012-10-22_at_7.32.07_PM.png 1.81 MB
   • Edit

7. Support Staff 7 Posted by brandi on 23 Oct, 2012 01:08 AM

   

   Thanks for this report, Ben. We didn't find anything suspicious in our records between 4:30-4:33 and I just ran a Staff Response report and got results pretty quickly.

   I'm going to have Julien look at your attachment in the morning to see if he finds anything of interest in there.

   Thanks,
   Brandi

   • Edit

8. 8 Posted by bhspencer on 23 Oct, 2012 08:39 PM

   

   Hi Brandi

   I thought I'd try the report again and got the same problem. Time 4:38pm EST

   • Edit

9. 9 Posted by bhspencer on 23 Oct, 2012 08:41 PM

   

   I would add that it isn't just me. All the other members of the support team I work on report the same problem. We are a diverse group running on a variety of OS and browser platforms, all working from how with different internet connections.

   Ben

   • Edit

10. 10 Posted by Julien on 23 Oct, 2012 09:57 PM

    

    Hi Ben,

    Thanks for the extra info. I think we have identified what's going wrong. I'll keep you posted once we have a fix.

    • Edit

11. Support Staff 11 Posted by Courtenay on 26 Oct, 2012 02:02 AM

    

    Howdy Ben,

    I rewrote a bunch of slow queries and added another dedicated database server just for reporting, and also killed a bug or two while we were up in there. It should be much faster for you now. Note that the old date handling code had a bug related to timezones, so (depending on how far away from GMT/UTC you are) some discussions and comments may now show in the day before or after. I believe it to have the correct behavior now.

    Courtenay

    • Edit

12. Courtenay closed this discussion on 26 Oct, 2012 02:02 AM.