Automation tips. File database brakes - how to avoid (from recent experience) 1s 8.3 is very slow
The 1C system today is one of the main tools for running small and medium-sized businesses. As a rule, all employees of the organization have access to the program. Thus, if 1C starts to slow down or work slowly, then this significantly affects the conduct of business. Let's look at how you can speed up and optimize work in 1C yourself.
Optimization using 1C update
New versions of 1C always work more successfully and quickly, so it is imperative to follow the updates. It is recommended to update your accounting records as often as possible. Especially when versions of regulated reporting are released.
Many people have been using the ability to automatically update the program for a long time. Although this issue can be easily resolved manually for 1C Enterprise 8.3, updating which will not cause any trouble.
The first step is to download the latest version of the platform you are currently using. This is done either using the ITS disk, or through the web interface, where they provide ongoing support to users of a program such as 1c Enterprise 8.3, a configuration update for which is also provided officially.
In the latter case, the archive with update data is downloaded separately. It is unpacked in any folder that is considered most convenient for the user. Then you need to run the .exe file. In the next window, simply click the “Next” button.
Another page will appear. On it, the user selects the path in which the installation is completed. But this step is recommended only for advanced personal computer owners. The default functions are usually sufficient to solve most problems. By default, in this case, one folder is specified where all updates are installed at once. This is much more convenient than when the final paths are different. We simply click on the “Next” buttons several times in the 1c Enterprise 8.3 program, the configuration of which should be updated quickly.
All that remains is the final button, which offers “Install”.
How to speed up 1C if the platform is slow
Problems most often result from the fact that at one of the stages the performer’s concentration of attention decreases. Here it is important to choose the right update scheme, only in this case we will not encounter a problem when 1c freezes during the update.
Version 7.7 update
There are several types of configuration. Depending on this, the course of further actions is chosen.
- Standard – in this case it is assumed that the update is also carried out for regulated reporting.
- Typical industry configurations are largely reminiscent of previous options. It is important to read the instructions provided by the developer in advance. Otherwise, you won’t be able to figure out why 1C 8.3 crashes during the update.
- Modified standard - the user always has the opportunity to modify the application himself so that it meets current needs. Another option for expanding functionality is moving to new platforms. For example, version 8.
About version 8.0 and 8.1
Currently, platform 8.0 is already being withdrawn from support. New standard developments will only work when using the latest versions. You just need to remember that all intermediate releases are completed without fail. Otherwise, there is a high probability of simply losing information. Or encounter a situation where 1c freezes when updating the configuration.
An option is possible when a new standard configuration is introduced, and then the remains from the old information databases are transferred to it.
As for version 8.1, you can update to it in several ways:
- manually;
- in automatic mode;
- contacting specialists from companies providing services in this area.
Working with non-standard or modified versions
Initially, any configuration refers to standard developments. It ceases to be such if certain changes are made at the enterprise. For example, during installation. There are two classes that stand out among non-standard configurations:
- changed;
- created from scratch, taking into account the needs of a specific enterprise.
Sometimes a second class configuration is actively distributed among users. Then it is considered typical. It’s just that the manufacturer is not considered to be 1C itself, but the company that created the new version.
Configurations can be kept up to date by the following actions:
- Error correction.
- Expansion of functionality.
- Improvement.
- Change 1s 8.3, the configuration is not updated in case of maintenance errors.
The installation process may take different times depending on the Internet speed at which you are currently using it. In a separate window, the user selects whether to update upon completion of work, or immediately. With the latter option, you need to make sure that no one else is working with the application. The process itself involves the use of exclusive mode within the 1c Enterprise 8.3 application, the latest update is no exception.
- We must remember that not all release versions may be suitable for the current configuration.
- If updates have not been carried out for a long time, you may have to download several files or archives at once.
- In the list it is easy to understand which version of 1C Enterprise 8.3 is needed, the update is selected by the user.
When the process is completed, the Configurator itself can be closed. This mode is most often used if an update is necessary. It is convenient and automates almost the entire process. When you launch it for the first time, a message may appear indicating that the platform is out of date. And that it is not recommended to use it at the current moment.
Additional reasons for braking
If the program is updated correctly and without any errors, however, 1C still slows down, then the reason may be the following:
- Antivirus - if configured correctly, no antivirus will interfere with the system, however, if you use factory settings, 1C performance may decrease by 5–10%. You can optimize your antivirus using additional settings by removing the background mode (if absolutely necessary).
- Computer parameters - often insufficiently powerful computers lead to a significant decrease in 1C performance. Particular attention must be paid to the video card, operating system and processor.
Such methods will significantly optimize and speed up work in 1C for any company or enterprise, after which the program’s performance will significantly increase.
How to increase the speed and ease of use in 1CPhoto by Alena Tulyakova, news agency “Clerk.Ru”
The article identifies the main mistakes that novice 1C administrators make and shows how to solve them using the Gilev test as an example.
The main purpose of writing this article is to avoid repeating obvious nuances for those administrators (and programmers) who have not yet gained experience with 1C.
The secondary goal is that if I have any shortcomings, Infostart will be the quickest to point this out to me.
V. Gilev’s test has already become a kind of “de facto” standard. The author on his website gave quite clear recommendations, but I will simply present some results and comment on the most likely errors. Naturally, the test results on your equipment may differ; this is just a guide for what should be and what you can strive for. I would like to note right away that changes must be made step by step, and after each step, check what result it gave.
There are similar articles on Infostart, I will put links to them in the relevant sections (if I miss something, please suggest me in the comments, I will add it). So, let’s assume your 1C is slow. How to diagnose the problem, and how to understand who is to blame, the administrator or the programmer?
Initial data:
Tested computer, main guinea pig: HP DL180G6, equipped with 2*Xeon 5650, 32 Gb, Intel 362i, Win 2008 r2. For comparison, the Core i3-2100 shows comparable results in the single-threaded test. The equipment I deliberately chose was not the newest; with modern equipment the results are noticeably better.
For testing separate 1C and SQL servers, SQL server: IBM System 3650 x4, 2*Xeon E5-2630, 32 Gb, Intel 350, Win 2008 r2.
To test a 10 Gbit network, Intel 520-DA2 adapters were used.
File version. (the database is on the server in a shared folder, clients connect via the network, CIFS/SMB protocol). Algorithm step by step:
0. Add Gilev’s test database to the file server in the same folder as the main databases. We connect from the client computer and run the test. We remember the result.
It is understood that even for old computers from 10 years ago (Pentium on 775 socket), the time from clicking on the 1C:Enterprise shortcut to the appearance of the database window should take less than a minute. (Celeron = slow).
If your computer is worse than a Pentium on 775 socket with 1 GB of RAM, then I sympathize with you, and it will be difficult for you to achieve comfortable work on 1C 8.2 in the file version. Think about either upgrading (it's high time) or switching to a terminal (or web, in the case of thin clients and managed forms) server.
If the computer is no worse, then you can kick the administrator. At a minimum, check the operation of the network, antivirus and HASP protection driver.
If Gilev’s test at this stage showed 30 “parrots” or higher, but the 1C working base still works slowly, the questions should be directed to the programmer.
1. As a guide to how much a client computer can “squeeze”, we check the operation of only this computer, without a network. We install the test database on a local computer (on a very fast disk). If the client computer does not have a normal SSD, then a ramdisk is created. For now, the simplest and free one is Ramdisk enterprise.
To test version 8.2, a 256 MB ramdisk is enough, and! The most important. After rebooting the computer, with the ramdisk running, there should be 100-200 MB free on it. Accordingly, without a ramdisk, for normal operation there should be 300-400 MB of free memory.
To test version 8.3, a 256 MB ramdisk is enough, but you need more free RAM.
When testing, you need to look at the processor load. In a case close to ideal (ramdisk), local file 1c loads 1 processor core when running. Accordingly, if during testing your processor core is not fully loaded, look for weak points. A little emotional, but generally correct, the influence of the processor on the operation of 1C is described. Just for reference, even on modern Core i3s with high frequencies, the numbers 70-80 are quite realistic.
The most common errors at this stage.
- Incorrectly configured antivirus. There are many antiviruses, the settings for each are different, I will only say that with proper configuration, neither the web nor Kaspersky 1C interferes. With the default settings, approximately 3-5 parrots (10-15%) can be taken away.
- Performance mode. For some reason, few people pay attention to this, but the effect is the most significant. If you need speed, then you must do this, both on client and server computers. (Gilev has a good description. The only caveat is that on some motherboards, if you turn off Intel SpeedStep, you cannot turn on TurboBoost).
You can (and preferably) enable performance mode in two places:
- via BIOS. Disable modes C1, C1E, Intel C-state (C2, C3, C4). In different bios they are called differently, but the meaning is the same. It takes a long time to search, a reboot is required, but if you do it once, then you can forget it. If you do everything correctly in the BIOS, the speed will increase. On some motherboards, you can configure the BIOS settings so that Windows performance mode will not play a role. (Examples of BIOS settings from Gilev). These settings mainly concern server processors or “advanced” BIOSes, if you haven’t found this and you DO NOT have Xeon, that’s okay.
- Control panel - Power supply - High performance. Minus - if the computer has not been serviced for a long time, it will make a louder fan noise, heat up more and consume more energy. This is a performance fee.
| These are the default settings. BIOS C-state enabled, balanced power consumption mode |  |
| BIOS C-state enabled, high performance mode For Pentium and Core you can stop there, You can still squeeze a little "parrots" out of Xeon |  |
| In BIOS C-state is disabled, high performance mode. If you don't use Turbo boost, this is what it should look like server tuned for performance |  |
And now the numbers. Let me remind you: Intel Xeon 5650, ramdisk. In the first case, the test shows 23.26, in the last - 49.5. The difference is almost twofold. The numbers may vary, but the ratio remains essentially the same for Intel Core.
Dear administrators, you can criticize 1C as much as you like, but if end users need speed, you need to enable high performance mode.
c) Turbo Boost. First you need to understand whether your processor supports this function, for example. If it supports, then you can still quite legally get some performance. (I don’t want to touch on the issues of frequency overclocking, especially servers, do it at your own peril and risk. But I agree that increasing Bus speed from 133 to 166 gives a very noticeable increase in both speed and heat dissipation)
How to turn on turbo boost is written, for example, . But! For 1C there are some nuances (not the most obvious). The difficulty is that the maximum effect of turbo boost occurs when C-state is turned on. And we get something like this:
Please note that the multiplier is the maximum, the Core speed is beautiful, and the performance is high. But what will happen as a result with 1s?
But in the end it turns out that according to CPU performance tests the version with a multiplier of 23 is ahead, according to Gilev’s tests in the file version the performance with a multiplier of 22 and 23 is the same, but in the client-server version - the version with a multiplier of 23 is terrible terrible terrible (even if C -state set to level 7, it is still slower than with C-state turned off). Therefore, the recommendation is to check both options for yourself and choose the best one. In any case, the difference between 49.5 and 53 parrots is quite significant, especially without much effort.
Conclusion - turbo boost must be turned on. Let me remind you that it is not enough to enable the Turbo boost item in the BIOS, you also need to look at other settings (BIOS: QPI L0s, L1 - disable, demand scrubbing - disable, Intel SpeedStep - enable, Turbo boost - enable. Control Panel - Power Options - High Performance) . And I would still (even for the file version) choose the option where c-state is turned off, even though the multiplier is smaller. It will turn out something like this...
A rather controversial point is the memory frequency. For example, memory frequency is shown to have a very strong influence. My tests did not reveal such a dependence. I will not compare DDR 2/3/4, I will show the results of changing the frequency within the same line. The memory is the same, but in the BIOS we are forced to set lower frequencies.
 |  |  |
And test results. 1C 8.2.19.83, for the file version local ramdisk, for client-server 1C and SQL on one computer, Shared memory. Turbo boost is disabled in both versions. 8.3 shows comparable results.
The difference is within the measurement error. I specifically pulled out screenshots of CPU-Z to show that with a change in frequency, other parameters also change, the same CAS Latency and RAS to CAS Delay, which neutralizes the change in frequency. The difference will be when the memory modules are physically changed, from slower to faster, but even there the numbers are not particularly significant.
2. When we have sorted out the processor and memory of the client computer, we move on to the next very important place - the network. Many volumes of books have been written about network tuning, there are articles on Infostart (, and others), but here I will not focus on this topic. Before starting testing 1C, please make sure that iperf between two computers shows the entire bandwidth (for 1 Gbit cards - well, at least 850 Mbit, or better yet 950-980), that Gilev’s advice has been followed. Then - the simplest test of operation will be, oddly enough, copying one large file (5-10 gigabytes) over the network. An indirect sign of normal operation on a 1 Gbit network will be an average copying speed of 100 MB/sec, good operation - 120 MB/sec. I would like to draw your attention to the fact that the weak point (including) may be the processor load. The SMB protocol on Linux is quite poorly parallelized, and during operation it can quite easily “eat up” one processor core and not consume any more.
And further. With the default settings, the windows client works best with a windows server (or even a windows workstation) and the SMB/CIFS protocol, a linux client (debian, ubuntu didn’t look at the others) works better with linux and NFS (it also works with SMB, but on NFS parrots are taller). The fact that during linear copying a Windows Linux server to NFS is copied into one stream faster does not mean anything. Debian tuning for 1C is a topic for a separate article, I’m not ready for it yet, although I can say that in the file version I got even slightly better performance than the Win version on the same equipment, but with postgres with over 50 users I still have everything very bad.
The most important thing that “burnt” administrators know, but beginners do not take into account. There are many ways to set the path to the 1c database. You can do servershare, you can do 192.168.0.1share, you can net use z: 192.168.0.1share (and in some cases this method will also work, but not always) and then specify drive Z. It seems that all these paths point to the same thing the same place, but for 1C there is only one method that provides normal performance quite reliably. So, this is what you need to do correctly:
On the command line (or in policies, or whatever is convenient for you) - do net use DriveLetter: servershare. Example: net use m: serverbases. I specifically emphasize NOT the IP address, but the server name. If the server name is not visible, add it to the dns on the server, or locally to the hosts file. But the address must be by name. Accordingly, on the way to the database, access this disk (see picture).
And now I will show with numbers why this is the advice. Initial data: Intel X520-DA2, Intel 362, Intel 350, Realtek 8169 cards. OS Win 2008 R2, Win 7, Debian 8. Latest drivers, updates applied. Before testing, I made sure that Iperf gives the full bandwidth (except for 10 Gbit cards, it only managed to squeeze out 7.2 Gbit, I’ll see why later, the test server is not yet configured properly). The disks are different, but everywhere there is an SSD (I specially inserted a single disk for testing, it is not loaded with anything else) or a raid from an SSD. The speed of 100 Mbit was obtained by limiting the settings of the Intel 362 adapter. There was no difference between 1 Gbit copper Intel 350 and 1 Gbit optical Intel X520-DA2 (obtained by limiting the speed of the adapter). Maximum performance, turbo boost is turned off (just for comparability of results, turbo boost for good results adds a little less than 10%, for bad results it may not have any effect at all). Versions 1C 8.2.19.86, 8.3.6.2076. I don’t give all the numbers, but only the most interesting ones, so that you have something to compare with.
| 100 Mbit CIFS Win 2008 - Win 2008 contact by ip address | 100 Mbit CIFS Win 2008 - Win 2008 calling by name | 1 Gbit CIFS Win 2008 - Win 2008 contact by ip address | 1 Gbit CIFS Win 2008 - Win 2008 calling by name | 1 Gbit CIFS Win 2008 - Win 7 calling by name | 1 Gbit CIFS Win 2008 - Debian calling by name | 10 Gbit CIFS Win 2008 - Win 2008 contact by ip address | 10 Gbit CIFS Win 2008 - Win 2008 calling by name |
|
| 11,20 | 26,18 | 15,20 | 43,86 | 40,65 | 37,04 | 16,23 | 44,64 | |
| 1C 8.2 | 11,29 | 26,18 | 15,29 | 43,10 | 40,65 | 36,76 | 15,11 | 44,10 |
| 8.2.19.83 | 12,15 | 25,77 | 15,15 | 43,10 | 14,97 | 42,74 | ||
| 6,13 | 34,25 | 14,98 | 43,10 | 39,37 | 37,59 | 15,53 | 42,74 | |
| 1C 8.3 | 6,61 | 33,33 | 15,58 | 43,86 | 40,00 | 37,88 | 16,23 | 42,74 |
| 8.3.6.2076 | 33,78 | 15,53 | 43,48 | 39,37 | 37,59 | 42,74 |
Conclusions (from the table and from personal experience. Applies only to the file version):
- Over the network, you can get quite normal numbers for work if this network is properly configured and the path is entered correctly in 1C. Even the first Core i3 can easily produce 40+ parrots, which is quite good, and these are not only parrots, in real work the difference is also noticeable. But! The limitation when working with several (more than 10) users will no longer be the network, here 1 Gbit is still enough, but blocking during multi-user work (Gilev).
- the 1C 8.3 platform is many times more demanding in terms of proper network configuration. Basic settings - see Gilev, but keep in mind that everything can be influenced. I saw an acceleration from uninstalling (and not just turning off) the antivirus, from removing protocols like FCoE, from changing drivers to an older, but Microsoft certified version (especially for cheap cards like ASUS and DLC), from removing the second network card from the server . There are a lot of options, set up your network carefully. There may well be a situation where platform 8.2 gives acceptable numbers, and 8.3 - two or even more times less. Try playing with platform versions 8.3, sometimes you get a very big effect.
- 1C 8.3.6.2076 (maybe later, I haven’t looked for the exact version yet) is still easier to configure over the network than 8.3.7.2008. I was able to achieve normal operation over the network from 8.3.7.2008 (in comparable parrots) only a few times; I could not repeat it for a more general case. I didn’t understand much, but judging by the foot wraps from Process Explorer, the recording there is not as good as in 8.3.6.
- Despite the fact that when working on a 100 Mbit network, its load graph is small (we can say that the network is free), the operating speed is still much less than on 1 Gbit. The reason is network latency.
- All other things being equal (a well-functioning network) for 1C 8.2 the Intel-Realtek connection is 10% slower than Intel-Intel. But realtek-realtek can generally give sharp subsidence out of the blue. Therefore, if you have money, it’s better to keep Intel network cards everywhere; if you don’t have money, then install Intel only on the server (your CO). And there are many times more instructions for tuning Intel network cards.
- The default antivirus settings (using the example of drweb version 10) take about 8-10% of the parrots. If you configure it as it should (allow the 1cv8 process to do everything, although it is not safe), the speed is the same as without an antivirus.
- Do NOT read Linux gurus. A server with samba is great and free, but if you install Win XP or Win7 (or even better - server OS) on the server, then the file version of 1c will work faster. Yes, samba and the protocol stack and network settings and much, much more can be well tuned in debian/ubuntu, but this is recommended for specialists. There is no point in installing Linux with default settings and then saying that it is slow.
- It's quite a good idea to check the operation of disks connected via net use using fio . At least it will be clear whether these are problems with the 1C platform, or with the network/disk.
- For the single-user version, I can’t think of tests (or a situation) where the difference between 1 Gbit and 10 Gbit would be visible. The only thing where 10Gbit for the file version gave better results is connecting disks via iSCSI, but this is a topic for a separate article. Still, I think that for the file version 1 Gbit cards are enough.
- I don’t understand why, with a 100 Mbit network, 8.3 works noticeably faster than 8.2, but it was a fact. All other equipment, all other settings are absolutely the same, it’s just that in one case 8.2 is tested, and in the other - 8.3.
- Non-tuned NFS win-win or win-lin gives 6 parrots, I did not include them in the table. After tuning I got 25, but it was unstable (the difference in measurements was more than 2 units). I can’t yet give recommendations on using Windows and the NFS protocol.
Terminal server. (the database is on the server, clients connect via the network, RDP protocol). Algorithm step by step:
- We add Gilev’s test database to the server in the same folder as the main databases. We connect from the same server and run the test. We remember the result.
- In exactly the same way as in the file version, we configure the processor. In the case of a terminal server, the processor generally plays the main role (it is assumed that there are no obvious weak points, such as lack of memory or a huge amount of unnecessary software).
- Configuring network cards in the case of a terminal server has virtually no effect on the operation of 1c. To ensure “special” comfort, if your server produces more than 50 parrots, you can play with new versions of the RDP protocol, just for the comfort of users, faster response and scrolling.
- When a large number of users are actively working (and here you can already try connecting 30 people to one database, if you try), it is very advisable to install an SSD drive. For some reason, it is believed that the disk does not particularly affect the operation of 1C, but all tests are carried out with the controller cache enabled for writing, which is incorrect. The test base is small, it fits quite well in the cache, hence the high numbers. On real (large) databases everything will be completely different, so the cache is disabled for tests.
| Raid 10 4x SATA 7200 ATA ST31500341AS | Raid 10 4x SAS 10k | Raid 10 4x SAS 15k | Single SSD | Ramdisk | Ramdisk | Cache enabled RAID controller |
|
| 21,74 | 28,09 | 32,47 | 49,02 | 50,51 | 53,76 | 49,02 | |
| 1C 8.2 | 21,65 | 28,57 | 32,05 | 48,54 | 49,02 | 53,19 | |
| 8.2.19.83 | 21,65 | 28,41 | 31,45 | 48,54 | 49,50 | 53,19 | |
| 33,33 | 42,74 | 45,05 | 51,55 | 52,08 | 55,56 | 51,55 | |
| 1C 8.3 | 33,46 | 42,02 | 45,05 | 51,02 | 52,08 | 54,95 | |
| 8.3.7.2008 | 35,46 | 43,01 | 44,64 | 51,55 | 52,08 | 56,18 |
- The enabled RAID controller cache eliminates all the differences between the disks; the numbers are the same for both sat and cas. Testing with it on a small amount of data is useless and is not indicative of any kind.
- For platform 8.2, the difference in performance between SATA and SSD options is more than double. This is not a typo. If you look at the performance monitor during the test on SATA drives. then you can clearly see “Active disk operating time (in%)” 80-95. Yes, if you enable the cache of the disks themselves for recording, the speed will increase to 35, if you enable the cache of the raid controller - up to 49 (regardless of which disks are being tested at the moment). But these are synthetic cache parrots; in real work, with large databases, there will never be a 100% write cache hit ratio.
- The speed of even cheap SSDs (I tested on Agility 3) is quite enough to run the file version. The recording resource is another matter, you need to look at it in each specific case, it is clear that the Intel 3700 will have it an order of magnitude higher, but the price is corresponding. And yes, I understand that when testing an SSD disk, I also test the cache of this disk to a greater extent, the real results will be less.
- The most correct (from my point of view) solution would be to allocate 2 SSD disks in a mirrored raid for a file database (or several file databases), and not place anything else there. Yes, with a mirror, SSDs wear out equally, and this is a minus, but at least the controller electronics are somehow protected from errors.
- The main advantages of SSD drives for the file version will appear when there are many databases, each with several users. If there are 1-2 databases, and there are about 10 users, then SAS disks will be enough. (but in any case, look at loading these disks, at least through perfmon).
- The main advantages of a terminal server are that it can have very weak clients, and the network settings affect the terminal server much less (again, your K.O.).
If Gilev’s test shows small numbers, and you have a high-clock processor and fast disks, then the administrator needs to take at least perfmon, recording all the results somewhere, and watch, observe, and draw conclusions. There will be no definitive advice.
Client-server option.
Tests were carried out only on 8.2, because on 8.3 everything depends quite seriously on the version.
For testing, I chose different server options and networks between them to show the main trends.
| 1C: Xeon 5520 SQL: Xeon E5-2630 | 1C: Xeon 5520 SQL: Xeon E5-2630 Fiber channel - SSD | 1C: Xeon 5520 SQL: Xeon E5-2630 Fiber channel - SAS | 1C: Xeon 5650 SQL: Xeon E5-2630 | 1C: Xeon 5650 SQL: Xeon E5-2630 Fiber channel - SSD | 1C: Xeon 5650 SQL: Xeon E5-2630 | 1C: Xeon 5650 = | 1C: Xeon 5650 = | 1C: Xeon 5650 = | 1C: Xeon 5650 = | 1C: Xeon 5650 = | |
| 16,78 | 18,23 | 16,84 | 28,57 | 27,78 | 32,05 | 34,72 | 36,50 | 23,26 | 40,65 | 39.37 | |
| 1C 8.2 | 17,12 | 17,06 | 14,53 | 29,41 | 28,41 | 31,45 | 34,97 | 36,23 | 23,81 | 40,32 | 39.06 |
| 16,72 | 16,89 | 13,44 | 29,76 | 28,57 | 32,05 | 34,97 | 36,23 | 23,26 | 40,32 | 39.06 |
It seems that I have considered all the interesting options, if there is anything else you are interested in, write in the comments, I will try to do it.
- SAS on storage systems is slower than local SSDs, even though the storage systems have larger cache sizes. SSDs, both local and on storage systems, work at comparable speeds for Gilev’s test. I don’t know any standard multi-threaded test (not just recording, but all equipment) except for the 1C load test from the MCC.
- Changing the 1C server from 5520 to 5650 almost doubled the performance. Yes, the server configurations do not completely match, but it shows a trend (no surprise).
- Increasing the frequency on the SQL server certainly gives an effect, but not the same as on the 1C server; MS SQL server is excellent (if you ask it) to use multi-cores and free memory.
- Changing the network between 1C and SQL from 1 Gbit to 10 Gbit gives approximately 10% parrots. I expected more.
- Enabling Shared memory still gives an effect, although not 15%, as described in the article. Be sure to do it, fortunately it’s quick and easy. If during installation someone gave the SQL server a named instance, then for 1C to work, the server name must be specified not by FQDN (tcp/ip will work), not through localhost or just ServerName, but through ServerNameInstanceName, for example zz-testzztest. (Otherwise there will be a DBMS error: Microsoft SQL Server Native Client 10.0: Shared Memory Provider: The shared memory library used to establish a connection with SQL Server 2000 was not found. HRESULT=80004005, HRESULT=80004005, HRESULT=80004005, SQLSrvr: SQLSTATE=08001, state=1, Severity=10, native=126, line=0).
- For users less than 100, the only point in splitting it into two separate servers is a Win 2008 Std (and older) license, which only supports 32GB of RAM. In all other cases, 1C and SQL definitely need to be installed on one server and given more (at least 64 GB) memory. Giving MS SQL less than 24-28 GB of RAM is unjustified greed (if you think that you have enough memory for it and everything works fine, maybe the file version of 1C would be enough for you?)
- How worse the combination of 1C and SQL works in a virtual machine is the topic of a separate article (hint - noticeably worse). Even in Hyper-V everything is not so clear...
- Balanced performance mode is bad. The results are quite consistent with the file version.
- Many sources say that debugging mode (ragent.exe -debug) causes a significant decrease in performance. Well, it reduces, yes, but I wouldn’t call 2-3% a significant effect.
Does 1C start in two minutes? Does the document log take 40 seconds to open? Is the document held for almost a minute?
This is a familiar situation if you are using the file version with network access.
You can, of course, install a server and forget about the brakes, but if you only have 2-3 people working in 1C, and spending money on purchasing server licenses is not practical.
Symptoms:
The work of several users over the network with the same file (database) includes a network blocking mechanism. This forces the system to waste valuable time identifying open recording sessions and resolving conflicts accordingly. The main signs of blocking operation:
- fast user work with the database over the network in exclusive mode and extremely slow when several users work simultaneously.
- fast user work with a local database on the server and slow work over the network.
- The processor on the server is almost idle.
- Gigabit network card load is less than 5%.
- accesses to the file system are slightly less than 10 MB/sec.
- When trying to simultaneously post documents, one computer stalls for about a minute, and the second one crashes from 1C with the error text “failed to lock the table.”
- Starting 1C lasts about 3 minutes.
Tips that can help speed up the file database:
- Go to work in terminal access. Unfortunately, Windows 7 does not allow you to turn into a terminal server using standard tools - there is a maximum of one active connection. In this case, the remaining sessions do not terminate; you can reconnect under another user - “throwing out” the previous user, but without terminating his session. Therefore, you should transfer 1C to a server OS, where there are no such restrictions, or resolve the issue with a third-party utility.
- Disable the use of the IPv6 network protocol, configure addressing on the “old” IPv4.
- Add 1C processes to the Windows firewall exceptions, as well as to the antivirus exceptions, or disable them completely (more risky, but a simple test showed an increase in the speed of document retransfer with Avast antivirus disabled significantly!)
- Start indexing full-text search in 1C or turn it off completely
- Run testing and correction of the database, checking with the ChDbfl utility (the utility is located in the “bin” folder of the installed technology platform).
- Run the "Check configuration" item in the configuration (if the configuration is not standard, this may be useful).
- Disable unnecessary functional options (the less unnecessary in the managed interface, the faster it works, as a rule).
- Set up user rights (the less unnecessary in the managed interface, the faster it works, as a rule).
- Start recalculating the totals and restoring the sequence (a significant increase can only occur if the totals have not been restored for a long time).
- Specify "Connection speed - low" in the database list settings.
- Defragmentation of a disk with a file database.
- Database convolution (may be useful if the database is large, for example, for several years).
- Hardware upgrade - faster hard drive (SSD), new switch, processor, memory, etc.
- Install on a web server, access using a thin client.
After completing all these steps, the 1C file database can work much faster. In some cases, the launch took 10 seconds, and the speed of document processing increased 12 times.
P.S. In the UT 11.1 configuration, launching file 1C using network access to a shared folder is unrealistic, because Even the fastest solid-state drive, RAM and processor run into network locks, and the work of more than one user becomes virtually impossible.
Self-written small configurations can work quite quickly even in the file version.
Everyone who works with products on the 1C:Enterprise platform has probably heard the phrase “1C is slow.” Some people complained about it, others accepted complaints. In this article we will try to look at the most common causes of this problem and options for solving it.
Let's turn to a metaphor: before finding out why a person did not come somewhere, you should make sure that he has legs to walk. So, let's start with the hardware and network requirements.
If Windows 7 is installed:
If Windows 8 or 10 is installed:
Also remember that there must be at least 2GB of free disk space, and the network connection must have a speed of at least 100 MB/sec.
It doesn’t make much sense to consider the characteristics of servers in the client-server version, because in this case everything depends on the number of users and the specifics of the tasks that they solve in 1C.
When choosing a server configuration, keep the following in mind:
- One 1C server worker process consumes an average of 4 GB (not to be confused with a user connection, since one worker process can have as many connections as you specify in the server settings);
- Using 1C and a DBMS (especially MS SQL) on one physical server gives benefits when processing large amounts of data (for example, closing a month, calculating a budget based on a model, etc.), but significantly reduces performance during unloaded operations (for example, creating and conducting implementation document, etc.);
- Remember that 1C servers and the DBMS must be connected over a channel “thick” of 1 GB;
- Use high-performance disks and do not combine the 1C server and DBMS roles with other roles (for example, file, AD, domain controller, etc.).
If after checking the equipment 1C still “slows down”
We have a small company, 7 people, and 1C is slow. We contacted specialists, and they said that only the client-server option would save us. But for us such a solution is not acceptable, it is too expensive!
Carry out routine maintenance in the database*:
1. Launch the database in configurator mode.
2. Select “Administration” in the main menu, and in it – “Testing and correction”.
3. Check all the boxes as in the picture. Click Run.
*This procedure may take from 15 minutes to an hour depending on the size of the database and the characteristics of your PC.
If this does not help, then we make a client-server connection, but without additional investments in hardware and software:
1. Choose the least loaded desktop computer in the office (not a notebook): it must have at least 4 GB of RAM and a network connection of at least 100 MB/sec.
2. Activate IIS (Internet Information Server) on it. For this:
3. Publish your database on this computer. There is available material on this topic on ITS, or contact a support specialist.
4. On user computers, configure access to the database through a thin client. For this:
Open the 1C launch window.
Select your work base. Here it is “Your Base”. Click "Edit". Set the switch to the “On a web server” position, indicate in the line below the name or IP address of the server on which IIS was activated, and the name under which the database was published. Click "Next".
Set the "Basic startup mode" switch to "Thin Client" mode. Click "Done".
We have a rather large company, but not a very big one, about 50–60 people. We use a client-server option, but 1C is terribly slow.
In this case, it is recommended to split the 1C server and the DBMS server into two different servers. When separating, be sure to remember: if they remained on the same physical server, which was simply virtualized, then the disks of these servers must be different - physically different! Also, be sure to set up routine tasks on the DBMS server when it comes to MS SQL (more details about this are described on the ITS website)
We have a rather large company, more than 100 users. Everything is configured in accordance with 1C recommendations for this option, but when processing some documents, 1C is very slow, and sometimes a blocking error occurs. Maybe do a base rollup?
A similar situation arises due to the size of a very specific accumulation or accounting register (but more often - accumulation), due to the fact that the register either “closes” altogether, i.e. there are incoming movements, but no flow movements, or the number of measurements by which the register balances are calculated is very large. There may even be a mix of the two previous reasons. How to determine which register is ruining everything?
We record the time when documents are processed slowly, or the time and user who has a blocking error.
Open the registration log.
We find the document we need, at the right time, for the right user with the event type “Data.Post”.
We look at the entire block of execution until the transaction is canceled if there was a blocking error, or we look for the longest change (the time from the previous record is more than a minute).
After this, we make a decision, keeping in mind that collapsing this particular register is in any case cheaper than the entire database.
We are a very large company, more than 1000 users, thousands of documents per day, our own IT department, a huge fleet of servers, we have optimized queries several times, but 1C is slow. We have apparently outgrown 1C, and we need something more powerful.
In the vast majority of such cases, it is not 1C that is slowing down, but the architecture of the solution used. When choosing a new business program, remember that writing your business processes in a program is cheaper and easier than converting them to some, especially a very expensive program. Only 1C provides this opportunity. Therefore, it is better to ask the question: “How to correct the situation? How can you make 1C “fly” at such volumes?” Let's briefly look at several treatment options:
- Use parallel and asynchronous programming technologies that 1C supports (background jobs and queries in a loop).
- When designing the solution architecture, avoid using accumulation registers and accounting registers in the most bottleneck areas.
- When developing a data structure (accumulation and/or information registers), adhere to the rule: “The fastest table for writing and reading is a table with one column.” What we are talking about will become clearer if you look at the typical RAUSE mechanism.
- To process large volumes of data, use auxiliary clusters where the same database is connected (but in no case should this be done during interactive work!!!). This will allow you to bypass standard 1C locks, which will make it possible to work with the database at almost the same speed as when working directly with SQL tools.
It is worth noting that 1C optimization for holdings and large companies is a topic for a separate, large article, so stay tuned for updated materials on our website.
Users often complain that “1C 8.3 is slow”: document forms open slowly, documents take a long time to process, the program starts, reports take a long time to generate, and so on.
Moreover, such “glitches” can occur in different programs:
The reasons may be different. This is not restored documents, a weak computer or server, the 1C server is incorrectly configured.
In this article I want to look at one of the simplest and most common reasons for a slow program - . This instruction will be relevant for users of file databases for 1-2 users, where there is no competition for resources.
If you are interested in more serious optimization of client-server options for system operation, visit the section of the site.
Where are the scheduled tasks in 1C 8.3?
Before I had time to load the program, many background tasks were completed in 1C. You can view them by going to the “Administration” menu, then “Support and Maintenance”:
Get 267 video lessons on 1C for free:
This is what the window with completed tasks looks like:
And here is a complete list of all scheduled tasks that are launched:
Among these tasks are such as ““, loading various classifiers, checking the relevance of the program version, and so on. For example, I have no use for almost all of these tasks. I don’t keep currency records, I control the versions myself, and load classifiers as needed.
Accordingly, it is in my (and in most cases in your) interests to disable unnecessary tasks.