It was my first time to import 223 transactions at an instance and it took eternity to import it into an account. It seems there is a major architecture problem which is making it too slow. In short, time taken doesn't seems to be linear to the number of transactions to be imported. Can you please fix this?
While I understand this must be very frustrating and limiting the usefulness of the importer, we are not using the urgency field to prioritize bugs so I have reverted the state back to normal. As for fixing it, can you please give some more details about when exactly you see this slowdown ? Which page of the import assistant were you on, what were you doing or what did you ask gnucash to do resulting in gnucash becoming slow ?
I used import-csv-transactions feature to import 223 transactions from last year till date. Following is the sample format of my csv data: 26-06-17,AMAZON ONLINE D S PVT BANGALORE IN,Expenses:ImportedTranx,3999 Note: Date format in my gnucash is as follows: 26/07/2017 After I hit "Apply" button, Gnucash became non-responsive. I could see that gnucash was consuming cpu and memory. I had to left my machine for more than 2 hours, then it gave me imported data with a dialogue of selecting/deselecting transactions. Please feel free if you need more information from my side. Thanks for working on this. If you can guide me, I can try to fix this issue as I'm a C/C++ software developer.
You are certainly welcome to help out getting this fixed. Unfortunately based on your description I still can't infer where exactly in the csv import the delay happens. There are to pages in which you can work with transactions, but neither is presented *after* clicking "Apply". There is the "Preview" page (for which I find the name is missing in the left-hand side list of pages). This page allows you to tweak import settings like date format, csv separators and so on. And there is the transaction matcher page. This page lists all detected transactions in either red, green or yellow. On this page you can tweak which transactions are new, or pre-existing. This page is the only page having an "Apply" button, but to get to this page you had to click a "Next" button. To point you in the right direction I'd want to be sure I'm with you on the same page.
Yes, I'm talking about the time when I hit "Apply" button on the page you have mentioned above.
I am sure this will be a question at some point, what is your Gnucash backend, are saving to a local xml file or sqlite file, myqsl server, network drive ?
(In reply to Vivek Agrawal from comment #4) > Yes, I'm talking about the time when I hit "Apply" button on the page you > have mentioned above. So that is *after* you have modified transaction selections (changing lines to green or red as fit) ? That would mean this is somewhere inside the generic import matcher. This is activated starting here: https://github.com/Gnucash/gnucash/blob/3.2/gnucash/import-export/csv-imp/assistant-csv-trans-import.cpp#L2057 If it happened right before you get to this page, it would be the delays happen in preparing for this page. The function that does the preparation is here: https://github.com/Gnucash/gnucash/blob/3.2/gnucash/import-export/csv-imp/assistant-csv-trans-import.cpp#L1972
As I have a Windows test machine available as of recently, I have run an import test on GnuCash 3.5. The test file is 300 lines. When hitting "Apply", it takes about half a minute to import them all. That doesn't seem unreasonable ? Have you been able to test this with a more recent GnuCash version ? A number of memory performance issues have been fixed since gnucash 3.2.
> I am sure this will be a question at some point, what is your Gnucash backend, are saving to a local xml file or sqlite file, myqsl server, network drive ? Good question that was not answered for either situation.
Indeed, and it has been almost a year. @Vivek Agrawal, if at some point you're able to reproduce this and answer the questions please reopen it and provide the answers.
