Increasingly slow performance in Web App

As my number of accounts and financial transactions continue to grow over time, I notice the YNAB web application seems to be slower and slower.  There's an increasing delay between when I submit an action and it completes, allowing me to continue working.  

- I do not experience this in the mobile app.

- Is there a recommended size I should work to keep my budget under? (# of accounts, # of transactions?)

- Is there a way to backup a budget (not export, backup) and then truncate transactions before a certain date (automatically putting in the balance as of that date for each account)?  This would allow me to (1) not lose my data if I wanted to get back to it, and (2) allow me to quickly try if a smaller budget file would improve performance.

 

Thanks,

Shawn

21replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Since you only experience it on the web app, I would check things like clearing your browser cache or switching to a different browser & seeing if that makes a difference.

    Reply Like
  • Coral Flute said:
    - Is there a way to backup a budget (not export, backup) and then truncate transactions before a certain date (automatically putting in the balance as of that date for each account)?  This would allow me to (1) not lose my data if I wanted to get back to it, and (2) allow me to quickly try if a smaller budget file would improve performance.

     There is no backup and restore function in the current version of YNAB.  There is no "save as" function.  If either of these existed, I would be willing to explain how I manually chopped down the budget to arbitrary starting date.  But I did that in YNAB 3 and YNAB 4, where I had a "save as" function and could start over if I made a mistake.  (Sometimes I had to start over.  I don't think I ever had to start over twice for the same episode of chopping down the budget.)  The risk of trashing my actual working budget if I make a mistake in the web version is simply too great for me to attempt this right now.

    If I arrive at a place where it slows noticeably as you report, I might bite the bullet and do it anyway.  First, I'd try things like closing my browser and restarting, using a different browser, or using my Linux computer side by side with my Windows computer to isolate whether it's really a budget issue or simply a computer memory issue.  Assuming a true budget issue . . . I'd chop it down.  I'd be very, very afraid of making a  mistake, but I'd do it anyway.

    In passing, I recall another user mentioning that her budget slowed to a crawl when she budgeted too many months in the future.  It's been a while since she did that, so it might not still be a thing.  I don't budget more than one month into the future, so I have never personally experienced that particular phenomenon.

    Reply Like
  • Do you have reconciled transactions filtered out from your account views? I suspect you probably already did this, but I mention it just in case; things get real slow when I view reconciled transactions, and then speed back up when I hide them.

    Reply Like
  • Thanks for the prompt replies!

    Have filtered view to just reconciled and/or a shorter time periods... performance is not significantly improved, perhaps slightly better.  Just slow entering in transactions, always a lag.  Additionally, my budget always takes a while to load (not because of internet connection speed), such that the browser prompts me with a "Web page is slowing down your browser" message, prompting me to Stop the page from loading (which prevents YNAB from working).

    - tried different browsers

    - not going to try Linux (just don't have the environment available)

    - I don't budget more than one month ahead... that's interesting that was causing a problem.

    - The lack of a "Save As..." is very limiting... Would give me confidence in trying a different solution.  The "Fresh Start" option is a bit too... fresh.  Also nervous about deleting and getting the single copy of my budget "right" afterwards.

    Reply Like
  • Coral Flute said:
    such that the browser prompts me with a "Web page is slowing down your browser" message, prompting me to Stop the page from loading

     This is usually a sign that the underlying client-side logic (the stuff that runs in your browser, not on the server) for a web app requires more computing resources than you have available. In other words you may need to close other things on your computer or get a more powerful computer.

    Reply Like
  • I agree that it's potentially related to computing resources, and thought it was an older computer (hardware) issue.  Current work laptop has a late model 4 core i7-8650 CPU and 32 GB of ram, SSD for the hard disk, and still experiencing the slowness.

    When the page is initially loading (slowly), the processor is at 25% for browser (Firefox in this trial), which indicates to me that it is using up one of the cores completely.  Processor drops down to less than 1% when complete.

    As my hardware is fairly up to date, my thinking was that it was an "amount of data" issue.

    How much data?  Records are from Jan 2012 to  Mar 2019 (so 7 years). 14,000 records in the register export. 7,900 records in the budget export.

    Reply Like
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 7 mths ago
      • Reported - view

      Coral Flute Amount of data and require processing needs are somewhat related. Also memory leaks in core JS app they use could be problematic.

      Reply Like
      • PapaShawn
      • papashawn
      • 7 mths ago
      • 1
      • Reported - view

      nolesrule Agree... which is why I'm trying to surface the issue. :-)  I know I'm not modifying the javascript.

      Reply Like 1
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 7 mths ago
      • 1
      • Reported - view

      Coral Flute I guess we'll just have to agree to agree. 😉

      Reply Like 1
      • Patzer
      • Retired at age 60. Thank you, YNAB!
      • Patzer
      • 7 mths ago
      • 1
      • Reported - view

      PapaShawn 

      PapaShawn said:
      How much data?  Records are from Jan 2012 to  Mar 2019 (so 7 years). 14,000 records in the register export. 7,900 records in the budget export.

       Hmm.  I had a YNAB budget starting in January 2012.  I chopped it down to start January 2017 before migrating to nYNAB to start learning that system in earnest in January 2018.  But the chop down was done in YNAB 4, where I do have "save as" to protect me.

      Here's a low risk experiment:  Note your account and category balances as of March 31.  Note whatever you've budgeted in April and spent since March 31.  Do a fresh start.  Populate your accounts with the balances as of March 31, and budget March to be the end of March category available balances.  Then replicate the budgeting you've done for April and any transactions these last few days.

      Does it speed up?  Then the size of data was the problem.  Does it stay slow?  Then something else was the problem.  In either case, you can rename the archived budget that Fresh Start created back to be your working budget.

      When I want to chop down a budget, I go through a conceptually similar manual process:  Pick a month to go back to, say January 2018.  Note account and category balances as of December 2017.   (I guess you need Toolkit for this now, because the base YNAB package doesn't have a running balance.)  Delete all transactions prior to January 1, 2018.  Delete all budgeting prior to January 2018.  Re-create starting balance transactions as of December 31, 2017 for the end of December account balances.  Budget December 2017 to be equal to my December 2017 category balances.  If I've done everything correctly, my ending budget has the same account and category balances that I started from.  I'm then free to delete any accounts and categories that I might have previously hidden, assuming they have no budget or transactions after my selected budget start date.

      But there's enough chances in there to make a mistake that I don't really want to do that again until I have to, or until such time that YNAB gives us a "save as" or "restore from backup" function.

      Reply Like 1
      • bevocat
      • Sometimes, It Just Sucks to Be You
      • bevocat
      • 7 mths ago
      • 1
      • Reported - view

      Patzer Would it not work as a test to create a new budget? You could pretend that was your "Fresh Start" and see if things move quicker once you have all your accounts set up and categories and so forth?

      Reply Like 1
      • Patzer
      • Retired at age 60. Thank you, YNAB!
      • Patzer
      • 7 mths ago
      • Reported - view

      bevocat It would work, but Fresh Start save you from having to set up accounts and categories.  Several times, I've done a Fresh Start, renamed it to something else to play with a budget, then renamed the backup to be my working budget again.

      I don't know whether the Fresh Start retains any Direct Import settings, because I don't use those.

      Reply Like
      • bevocat
      • Sometimes, It Just Sucks to Be You
      • bevocat
      • 7 mths ago
      • Reported - view

      Patzer Makes sense, and I've done the same thing.

      Reply Like
  • Patzer said:
    But there's enough chances in there to make a mistake that I don't really want to do that again until I have to, or until such time that YNAB gives us a "save as" or "restore from backup" function.

     I hear you.  Also not comfortable with the potential for an "oops" on my part.

    Thanks for detailing out the process you would use to chop/prune a budget! 🙂

    Reply Like 1
      • Patzer
      • Retired at age 60. Thank you, YNAB!
      • Patzer
      • 7 mths ago
      • Reported - view

      PapaShawn 

      Forgot to say, but part of my motivation in chopping down the budget last time was to avoid potential issues of the variety you report.  The other part was, I had several accounts that had been closed and categories I no longer needed in retirement.  Starting in 2017 let me eliminate that clutter, while keeping all history would mean the best I could do would be to hide it.

      Reply Like
      • casner
      • Now retired, and figuring out transitions
      • casner
      • 6 mths ago
      • Reported - view

      Patzer Since I am retiring in July (August with vacation) I am thinking of a Fresh Start myself. Did you wait a bit to see what categories made sense first?

      Reply Like
      • Patzer
      • Retired at age 60. Thank you, YNAB!
      • Patzer
      • 6 mths ago
      • Reported - view

      casner I retired at the end of August 2016, and chopped down the budget to start with December 31, 2016 balances, first real budget month January 2017.  By that time, I had got all my retirement income lined up, closed accounts that were no longer needed, and de-funded some categories that were no longer needed.  Most of my existing categories still made sense, but chopping it down let me delete Alimony (last payment, March 2015) and Emergency Fund (conceived as Income Replacement, sent the balance to investments to produce income.)  It wasn't so much the accounts that went away with retirement, or the E-Fund category; it was the accumulation of gradual changes in my financial life between 2012 and 2016 that added up to enough dead wood in accounts and categories that I wanted to delete some of them.

      Adding new accounts or finding new categories that are needed isn't as big a deal.  It's pretty easy to add new accounts and new categories to an existing budget.  Deleting categories and accounts that I haven't used for months or years and don't expect to use again is what requires the budget chop down or the fresh start.  Either that, or hide them and live with the storage overhead.

      Reply Like
  • Lots of great suggestions here! We haven't seen widespread reports of slowed-down budgets, but here's some of the most common causes/fixes:

     

    First, are you fully reconciling all of your accounts? Check out our help doc for instructions on the complete Reconciliation process – it’s more than just clearing transactions!

    Second, does the speed improve if you turn on the filter to exclude reconciled transactions? Click on the 'Filter' button in the upper right to see that option.  I see mamster recommended this too, sorry if I missed what happened when you tried it! 

    Thirdly, if you have more than 800 payees that could be a factor in slowing things down. Head over to Manage Payees and De-select "Include in Payee list" for payees that you don't often use.

    Finally, if you try to use YNAB in another browser or a private window do you still see that same delay? 
    Let me know how it goes!
     

    Reply Like 1
  • I have the same problem. Have tried the same things. No dice. Just wanted to chime in that it may be more prevalent than you realize because people just haven't reported it or weren't sure where to report it.  I had over 1,000 payees, and I turned off auto-fill for those. No change. :(

    Reply Like
    • Hi MichelleBowden ! We really appreciate you letting us know, so if it is something bigger—we can jump on it! Since you mentioned you're able to use YNAB in another browser, I wanted to check a few things: 

      If you use a private window. Do you still see the issue? If not, you’ll want to go ahead and clear your cookies and cache (here are instructions for ChromeFirefoxSafari, and Internet Explorer). So that you know, you will lose certain information that your browser remembers, so you may have to reset logins, etc.

      If that doesn’t fix things, it can mean that a browser extension is causing problems. If you use any, go ahead and turn them off one at a time until you figure out which one is causing the problem. We’d love to know which one it is so that we can look into it!

      If none of that works (or you've already tried them), the above steps will help narrow things down for our bug squashing team. You can submit a Bug Report, and they'll investigate further!

      Reply Like
  • ...also, I get totally locked up in Chrome now, and I used to have no issues (a few months ago) with Chrome. I'm on a Mac (fully updated and plenty of speed). I am only able to use YNAB in Firefox these days...

    Reply Like
Like4 Follow
  • 4 Likes
  • 6 mths agoLast active
  • 21Replies
  • 306Views
  • 13 Following