Many factors can be the cause of database slowdown. We have checked our work and excluded the reasons that can negatively affect the speed of the database.
Therefore, we suggest that you check your IT infrastructure to find and, if possible, resolve the factors that lead to slow system performance.
1.Running 1C in a thin client:
If you work in 1C:FirstBit system via web-browser, it is recommended to install thin client (1С desktop application), as it works faster and more efficiently than via web-browser.
If you need to install 1С desktop application on your computer, you can create request to Hotline and our consultants will help you with the installation.
2. Setting of additional filters to narrow down the search area.
Please, note, that it is very important to set filters to every user, because, full searching from even one User affects other Users. It takes a lot of RAM on the Server’s side, and you have many documents in the system.
The manual is in the link: Configure List Option (Filter)
You will be able to pull any field to the header and then search for it. Therefore, system will search information only in companies’ column, and you may set the same for almost every column. It will help to fix the issue with slowness.
When you are searching everywhere, since there are many documents, the system might slow down. You can see it in logs, that searching leads to errors:
Please try the following steps in addition:
During the searching please set the periods in documents lists, as you probably have a lot of documents in them from previous years, this slows down the system a lot.
3. Scheduled and Background Jobs
Note: Please keep in mind that you can only perform these items if you have ERP data base configuration, in base with Accounting configuration the control and configuration of Scheduled and Backgrounds Jobs is done on the FirstBit side.
3.1. Background Jobs.
Open Administration - Scheduled and Background Jobs:
Open the background jobs tab and analyze which jobs are failed to execute or cancelled by the program or by the user.
In the screenshot below, you can see how to set filters to find such jobs. Double-click to open it and you can see the details of each error.
3.2. Scheduled Jobs.
Check background processes in your 1C:FirstBit database and make settings for their schedule:
Some jobs can be rescheduled to a more convenient time so as not to slow down the database during an active workday. For some jobs, you can set a longer interval between each repeat, which will also help to relieve the database.
4. Useless Data in Cache.
Often the cause of glitches and slowdown of the database is a messed up 1C cache. Cleaning the cache very often leads to restoration of adequate performance of the database.
We have a manual on how to Clear Cache, but you can use a simpler method.
4.1. The following method of cache cleaning is suitable if the client works through the application:
You need to start the database, having previously set the /ClearCache key in the startup parameters.
It is necessary to keep in mind:
1- after a single start the cache will be cleared and this key can be removed from the startup parameters, because if you constantly start with this key, the startup will last longer than without it;
2- if the client has several bases, then it is necessary to start each base with this key, because at startup only the cache of one particular base is cleared.
4.2. If you work through a browser, it is necessary to clear the browser cache.
Thanks for being a Firstbit Customer! #Slow database #Ways to run database smoothly.