I’ve used some locally made softwares before and they would get slow (taking afew seconds) to make reports of afew hundred entries. so we yearly reset it using an inbuilt feature that brings ending balances to beginning balances thus deleting everything, and it became fresh (usable) again (we would keep a backup before that though).
since manager doesn’t remove old entries, would it become slow? if yes, would the (close accounting period) make it faster?
There is no easy answer to this. If you use a desktop version then slowness if anything would deal with your system specifications (processor, ram and disk drive (SSD quicker).
Similar if you use Cloud or Server edition then it also depends on the bandwidth available (internet). That is similar to your current situation.
Having mentioned that. Manager is quick and remains quick until you reach the limits as mentioned. It is not the application but hardware and bandwith.
Manager uses an efficient underlying database so hundreds of transactions will not cause performance problems. I’m not aware of performance issues for the business Manager targets. Importing 10,000’s of inventory items or having 100’s of concurrent users may result in performance issues.
Without some information on your use case it is hard to say more.
I’ve been improving performance over the years and continue to do.
The limits are so high that 99% of businesses never reach them. For that 1%, I’m actually working on a feature that will allow you to purge historical data and re-establish new starting balances.
This is helpful to get rid of customers, suppliers or other accounts that haven’t been used for years and keep your accounting file cleaner.
That’s great to know 
I won’t worry about it then
Our business has afew hundred inventory items and around 100 customers … each year around 3000 invoices would be added
Those are really small numbers compared to Manager’s capabilities.
I am trying to simulate retail store data that I have handled into the Manager Application,
The number of Active Inventory reaches 70,000 items, with an average purchase of 500 Invoices in one month and average sales 2500 in 1 month.
In general, with normal use Application performance is very good.
During the test I got the error RequestTimedOut - The operation was canceled. in Reports - Inventory Quantity Summary
The other reports are good, only the Web Error Out of Memory in Reports - Custom Report is due to the limited memory (16GB) that I have.
The process takes a little time because the data is large, but this process does not interfere with the comfort of other users who are also working on the same data at the same time.
Good test.
Regarding:
Most likely this is not related to your 16GB but to SQLIte 2GB limit see Dynamic Memory Allocation In SQLite. Specifically:
To prevent problems, all SQLite internal memory allocations occur using thin wrapper functions that take a signed 64-bit integer size parameter. The SQLite source code is audited to ensure that all size computations are carried out using 64-bit signed integers as well. SQLite will refuse to allocate more than about 2GB of memory at one go. (In common use, SQLite seldom ever allocates more than about 8KB of memory at a time so a 2GB allocation limit is not a burden.) So the 64-bit size parameter provides lots of headroom for detecting overflows.
Alternatively it indeed is the 16GB as it says Web Error and that deals with the browser cache. If you have more tabs open, especially chrome takes lots of RAM. Try to clear chache, but it is indeed some practical limit, unlikely to be a reality for almost everyone.
I’m not really sure, the error is from my hardware side or from the server side, or from the request timeout settings in the application. I noticed this error when the web browser memory touched the 11GB value and the application had not completed the process.
My database size 94MB
Sorry but has nothing to do with the database size but with the records. If your close to 30k invoices include all the 70+k inventory items we talk about 2.1 billion basic entries (will be a multiple of that) that would require more than 2GB Dynamic Memory Allocation based on how the report is being generated. Anyway you proved the point that Manager can handle large databases but at some time will have some difficulty, especially when having to deal with the whole dataset at a time such as in report generation (view). I think that the browser cache is at fault here thinking about it further as limits reach pretty quickly when for example generating large reports such as GL Transaction Report.
Dividing data into several time periods can be a solution to this Custom Report problem.
I hope @lubos can look into the Reports - Inventory Quantity Summary problem, the error still occurs even though I have specified a smaller time period. The other Inventory Reports are running well.
