1s 8.3 how to work if the network is slow. Automation Tips

The speed of 1C is very important factor, which determines the time for accessing information in the database and working with it. Unfortunately, most small and medium-sized businesses equip their workplaces with old or cheap computers, believing that bookkeeping does not require many resources. Databases can be loaded in five minutes, and reports and statements can be generated in a couple of minutes. When the time comes to close a month, even if there are few documents, the wait can last up to 10 minutes, and you need to check everything so that there are no errors and the month does not have to be re-closed.

Speeding up 1C means speeding up the company’s business processes related to reflecting the facts of the enterprise’s life in the information base. If 1C works slowly, then this will somehow affect the work of the entire company and profit.

The article will be useful both to specialists and accountants. There are a number of ways to speed up 1C, based on system testing and performance measurements, fine-tuning servers, etc., but here we will describe the most simple methods, providing positive influence at operating speed 1C.

We are ready to carry out all the necessary measures to speed up your 1C and make your work pleasant and comfortable. To speed up 1C, leave a request and we will call you back.

Why is 1C slow?

When asking such a question to 1C specialists, you will always receive a whole set of assumptions. And most of them can really affect the speed of 1C on your computer. Let's try to figure out what are the reasons for low 1C performance and how to increase it.

All reasons can be divided into two groups regarding the 1C program: external And internal. Let's consider each group of reasons separately and highlight the main points that should be monitored and corrected to speed up 1C.

External reasons for slow operation of 1C

External reasons affecting the speed of 1C 8.3 include hardware, operational and software factors.

Hardware factor

In our experience, most often the reason for the slow operation of 1C is the poor technical equipment of computers. Using computers from 2002-2007, equipped with outdated hardware, it is difficult to process large amounts of data and visualize them. That's all from here possible consequences– not only 1C slows down, but also the browser, office editors, mail, and much more.

We can identify two main components in a computer that most strongly influence 1C performance - the processor and RAM.

Processors come with different numbers of cores and different clock speeds. The number of cores allows you to process several processes simultaneously, and the frequency is responsible for the processing speed of processes. The higher both indicators are, the better.

RAM allows you to store data in temporary memory, allowing programs to work with it. The larger the amount of RAM, the more data can be processed by the 1C program. Increasing RAM has a positive effect on all stages of working with 1C - from loading a program to uploading reports. However, the positive effect of increasing RAM is felt at small volumes. When changing from 2 GB to 4 GB, the difference is felt strongly, but if you increase the memory from 16 GB to 32 GB, you will not feel much of an increase in performance (the information is not relevant for 1C servers).

It is worth mentioning the video card. Here you can save money by installing a budget-level video card, since 1C programs are designed in monotonous colors without the use of unnecessary special effects.

No matter what work is done to speed up 1C, if you have little RAM (1 GB) or a weak processor (2200 GHz), you are unlikely to achieve a noticeable increase in speed. It's worth thinking about upgrading your computer.

View your computer's settings directly in brief You can right-click on the My Computer icon and select “Properties” there. You will see the processor used, its frequency, and the amount of RAM.

Operational factor

Operational factors include the type of operating system and power settings.

The most common operating systems are 32- and 64-bit. Latest systems(Windows 8.10) are mostly 64-bit. 32-bit systems have some limitations, the main one of which is a software limitation of the maximum available amount of RAM - approximately 3.5 GB. Even if you physically have 8 GB installed, the maximum you can use is 3.5 GB.

Setting up the power supply involves selecting the “Maximum performance” operating scheme. In different operating systems, the power settings are located in different places; in Windows, you can always find it in the control panel.

Software factor

Software factors include programs that limit the performance of 1C, or programs that share computer resources with 1C.

This factor is easiest to eliminate - while 1C is running, close all other programs that require large quantity resources (browsers, video players, games, etc.), and also add the 1C program to the exceptions of your antivirus. You should not load your computer with other programs while working with 1C. This will help improve 1C performance due to the fact that all computer resources will be sent to process computing processes in 1C.

Internal reasons for slow operation of 1C

TO internal reasons factors that affect the speed of 1C include unnecessary documents, software cache, and routine tasks.

To ensure that there is nothing unnecessary in the database, it is recommended to regularly delete objects marked for deletion, roll up the database for previous periods, and also disable unnecessary functions. In the latest versions of 1C, a Performance section has appeared on the Administration tab. On it you can disable optional functions at your discretion and increase the speed of 1C.

Cache is a storage of information that, in the opinion of the system, can be requested by the user with the greatest probability. But as they work in the system, users create new databases, new users, and stop using old databases. The cache from them remains in the system and can slow down 1C. We recommend that you regularly clear the 1C cache.

Regulatory and background jobs– processes running in the background (without displaying or confirming the user) necessary to maintain and update this or that information. For example, why update the bank classifier or exchange rates once an hour if foreign exchange transactions are carried out rarely, and after pre-loading the current exchange rates? By disabling such processes, we will unload the system and direct all available resources to calculate the operations that we need to run.

Client-server solutions 1C

For companies using a 1C server, increased productivity is associated with improving the server (host computer) and its proper configuration. Client computers may have minimum requirements to run 1C, because all calculations will be performed on the server. However, sometimes even a powerful server cannot cope with the simultaneous work of 5-10 users if the 1C server is not properly configured.

Unfortunately, consideration of server settings to improve 1C performance is not included in this article, since this requires certain skills and knowledge in the areas of networking and the principles of operation of 1C servers.

Conclusions

We have considered all possible sources of problems regarding the slow operation of 1C. By carrying out the appropriate procedures and following our recommendations, you will improve 1C performance and be able to maintain high speed program operation. Do not forget that low 1C productivity results in low employee productivity due to short, but frequent downtime in the most common operations.

We are ready to improve the performance of your 1C, using an integrated approach to solving this problem - we will conduct all the necessary tests and take initial performance indicators, analyze the current state of computers and networks, and then carry out the entire set of measures to speed up 1C and tell you how to maintain the system in excellent shape.

Speed up 1C right now!

1C: Accounting is one of the most famous and most convenient accounting programs. Proof of this is its widespread distribution in all areas of activity: trade, production, finance, etc.

Unfortunately, like everyone else computer programs in 1C: Accounting there are also various crashes and freezes. One of the most common problems is slow system operation.

In order to understand the reasons for its occurrence and try to solve them, today’s article was written.

Eliminating common causes of slow 1C operation

1. The most common reason for a slow program is a long time to gain access to the base 1C file, which is possible due to errors on the hard drive or due to poor quality of the Internet connection, if cloud technologies are used. There may also be problems with the antivirus system settings.

Solution: perform a scan to eliminate errors and defragment the hard drive. Test Internet access speed. If the readings are low (less than 1 Mb/s), contact the provider's TP service. Temporarily disable anti-virus protection and firewall in the anti-virus system.

2. Perhaps the slow operation of the program is due to large size database file.

To solve this problem open 1C in the “Configurator” mode, select “Administration” in the system menu, then “Testing and correction”. In the window, the “Compression of information database tables” item must be selected; the “Testing and correction” item below is active. Click "Run" and wait for the process to complete.

3. Next possible reason- outdated software or outdated version of the program itself.

Way out of this situation: update the operating system software or install the latest one on at the moment version of the 1C program. For preventative purposes, always update to the latest version, which eliminates errors from earlier configurations.

To install latest version 1C system, you need to enter the program in the “Configuration” mode, then from the menu go to “Service” -> “Service” -> “Configuration Update”, then select the default settings and click the “Update” button.

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 10 years ago (Pentium on 775 socket ) the time from clicking on the 1C:Enterprise shortcut to the appearance of the database window should pass less than a minute. ( Celeron = slow).

If you have a computer worse than a Pentium 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 high frequency the numbers 70-80 are quite realistic.

The most common errors at this stage.

a) 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.

b) 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. ( Good description at Gilev's. The only caveat is that on some motherboards, if you turn off Intel SpeedStep, you cannot turn on TurboBoost).

In short, while 1C is running, there is a lot of waiting for a response from other devices (disk, network, etc.). While waiting for a response, if the performance mode is enabled, the processor lowers its frequency. A response comes from the device, 1C (the processor) needs to work, but the first clock cycles are at a reduced frequency, then the frequency increases - and 1C again waits for a response from the device. And so - many hundreds of times per second.

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 use the BIOS settings so that the mode Windows performance 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, it’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.

How to check that the mode is enabled. Launch the task manager - performance - resource monitor - CPU. We wait until the processor is busy with nothing.

These are the default settings.

In BIOS C-state included,

balanced power consumption mode

In BIOS C-state included, 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 turned off, 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?

	Factor	Core speed (frequency), GHz	CPU-Z Single Thread	Gilev Ramdisk test file version	Gilev Ramdisk test client-server
Without Turbo boost
C-state off, Turbo boost				53.19	40,32
C-state on, Turbo boost			1080	53,13	23,04

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 the 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. SMB The 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 one more thing. 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 the topic of 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’m still doing everything very bad.

The most important , which “burned” administrators know, but beginners do not take into account. There are many ways to set the path to the 1c database. You can do \\server\share, you can do \\192.168.0.1\share, you can net use z: \\192.168.0.1\share (and in some cases this method will also work, but not always) and then specify the Z drive. It seems that all these paths point to the same place, but for 1C there is only one way that provides normal performance quite reliably. So, this is what you need to do correctly:

IN command line(or in policies, or as you prefer) - do net use DriveLetter: \\server\share. Example: net use m: \\server\bases. I specifically emphasize NOT the IP address, namely Name server. 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, test server not configured properly yet). 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.

	Win 2008 - Win 2008 contact by ip address	Win 2008 - Win 2008 Calling by name	Win 2008 - Win 2008 Contact by IP address	Win 2008 - Win 2008 Calling by name	Win 2008 - Win 7 Calling by name	Win 2008 - Debian Calling by name	Win 2008 - Win 2008 Contact by IP address	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.

Other than that equal conditions(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.

Default antivirus settings (using drweb version 10 as an example) take up about 8-10% of 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.

After all the settings and checks, we run the test again from the client computer and rejoice at the improved result (if it works). If the result has improved, there are more than 30 parrots (and especially more than 40), fewer than 10 users are working at the same time, and the working database is still slow - almost certainly a programmer problem (or you have already reached the peak capabilities of the file version).

Terminal server. (the database is on the server, clients connect via the network, RDP protocol). Algorithm step by step:

0. 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.

1. In the same way as in the file version, we set up the work. In the case of a terminal server, the processor generally plays the main role (it is assumed that there are no explicit weak points, such as lack of memory or a huge amount of unnecessary software).

2. Setting up 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.

3. If 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.

For example, I checked the operation of the Gilev test with different disk options. I installed the discs from what was at hand, just to show the tendency. The difference between 8.3.6.2076 and 8.3.7.2008 is small (in the Ramdisk Turbo boost version 8.3.6 produces 56.18 and 8.3.7.2008 produces 55.56, in other tests the difference is even smaller). Power consumption - maximum performance, turbo boost disabled (unless otherwise stated).

	Raid 10 4x SATA 7200 ATA ST31500341AS	Raid 10 4x SAS 10k	Raid 10 4x SAS 15k	Single SSD	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 with the Intel 3700 it will be an order of magnitude higher, but the price is corresponding. And yes, I understand that when testing an SSD drive, I also test in to a greater extent cache of this disk, the actual 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 don't put 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.).

Conclusions: if you run the Gilev test on a terminal server (from the same disk where the working databases are located) and at those moments when the working database slows down, and the Gilev test shows a good result (above 30) - then slow work The main worker base is most likely the programmer to blame.

If the Gilev 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 clear 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 options servers and the networks between them to show the main trends.

	SQL: Xeon E5-2630	SQL: Xeon E5-2630 Fiber channel - SSD	SQL: Xeon E5-2630 Fiber channel - SAS	SQL: Xeon E5-2630 Local SSD	SQL: Xeon E5-2630 Fiber channel - SSD	SQL: Xeon E5-2630 Local SSD	1C: Xeon 5650 =	1C: Xeon 5650 = Shared memory	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

Everything seems to be interesting options I’ve looked into it, if there’s anything else you’re interested in, write in the comments, I’ll try to do it.

SAS on storage systems works slower than local SSDs, even though the storage system has large sizes cache. 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% of parrots. I expected more.

Enabling Shared memory still gives an effect, although not 15%, as described. 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 ServerName\InstanceName, for example zz-test\zztest. (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) gives a significant decrease in performance. Well, it reduces, yes, but I wouldn’t call 2-3% a significant effect.

For various reasons, users of the 1C program from time to time encounter 1C performance problems. For example: a document takes a long time to process, a report takes a long time to generate, transaction errors, the program freezes, slow response to user actions, etc. By following our instructions, you can achieve significant success in the performance of the program and prevent exceeding the system limit. This is not a panacea for all ills, but most of the reasons for 1C slowdowns lie precisely in these issues.

1. Do not perform routine or background tasks while users are working

The first and main rule for system administrators is to schedule all background tasks to be completed outside of working hours. The system must be unloaded as much as possible in order to perform routine tasks (indexing, document processing, data uploading) and at the same time not interfere with users’ work. Neither the system nor the users will interfere with each other if they work at different times.

2. Do not exchange RIB data during the working hours of users

Although in lately companies abandon the exchange system RIB data in favor of the online mode and terminal access, it is not superfluous to remember that during uploading and downloading of exchange data it is impossible to carry out documents and full-time job in the program. If possible, this procedure, if it exists, should be performed at night using background jobs.

3. Increase PC performance in a timely manner, matching its power to real needs

Do not forget that the simultaneous operation of 30 and 100 users in the system produces different loads. Accordingly, if a quantitative increase in users is planned, the IT service should promptly consider with the company management the issue of expanding the machine fleet, purchasing additional memory or servers.

4. Software on which 1C runs

The 1C program is such that it works differently on operating systems. It is not known exactly why, but it is so. For example, the server version of a 1C database on Linux OS in conjunction with SQL Postgre works much slower than the same 1C database but on Windows OS in conjunction with MS SQL. The exact reasons for this fact are not known, but apparently somewhere deep in the 1C platform there are compatibility problems with operating systems and non-Microsoft DBMSs. It is also worth deploying the system on a 64-bit server if you plan to place significant loads on the database.

5. Database indexing

Internal procedure of the 1C program, which “combs” the system from the inside. Set it to run as a background routine task at night and be calm.

6. Disabling operational batch accounting

The point is that when operational implementation documents, movements are recorded in registers, including batch accounting registers. Recording of batch accounting registers when posting documents can be disabled in the program settings. Once a month, it will be necessary to start processing the posting of documents by batches, for example, at a time when the load on the database is the least or when the smallest number users.

7. RAM

Use the following formula:

RAM = (DB 1+DB 2+DB N) / 100 * 70

About 70% of the total physical volume of databases. 1C bases love to eat well RAM. Don't forget this.

8. If possible, optimize self-written reports and processing with imperfect and outdated codes

During the life of a company, there is a need for writing reports and processing, as well as modifications to manage business processes and extract specific information. It’s all these improvements that can cause glitches and slow down work, because... a) some Kulibins may have once written heavy, incorrect code that is difficult for the program to execute and requires significant effort to execute; b) the code in which the processing or report is written may have become obsolete and requires revision and reprogramming. Use the rule - the less we change something in the program, the better.

9. Clear cache

A regular server reboot sometimes solves problems with the outdated 1C cache. Just try it. Unloading can also help – loading the information base through the configurator. And the most recent cleaning of the cache of a specific user is deleting folders in the 1C system directory of the form: kexifzghjuhfv8j33hbdgk0. But deleting cached user folders is the last thing, because... In addition to removing garbage, clearing the cache has unpleasant consequences in the form of deleting saved report settings and the user menu interface.

10. Reducing the physical volume of databases

More base – more resources. Naturally. Use standard 1C tools to collapse the database. Think about the possibility of giving up five years of data to improve productivity. And if you still need data from the last five years, you can always use a copy of the database.

11. Correct organization of architecture

In general, the architecture of the corporate information system must be correct. What do we mean by the right system? Comparability of the tasks assigned to the system with the available equipment and software. Plan the system together with: the system administrator (because he knows the machine fleet), the 1C programmer (because he knows the resource needs of 1C) and the head of the company (because he knows about the future growth or contraction of the company).

How to speed up work in 1C: Accounting 8.3 (edition 3.0) or disable routine and background tasks

2019-01-15T13:28:19+00:00

Those of you who have already switched to the new edition of 1C: Accounting 8.3 (edition 3.0) have noticed that it has become slower than 2. Some strange slowdowns, endless background tasks several times a day, which no one asked her to perform without our knowledge.

My accountants told me immediately after the transition that the new edition of 1C: Accounting 3.0 is downright slow compared to the previous ones! And it’s simply impossible to work.

I started looking into it and very soon found out that the main reason for freezes and subsequent user dissatisfaction are routine and background tasks, many of which are enabled by default, although for the vast majority of accountants there is no need for them.

Well, for example, why do we need to run the “Text Extraction” task a hundred times a day if we do not perform a full-text (accountants, don’t be alarmed) search across all objects in our database.

Or why constantly download currency rates if we do not have currency transactions or we do them occasionally (and before that we ourselves can click the download rates button).

The same applies to 1C’s constant attempt to connect to the site and check and update bank classifiers. For what? I myself will press the button to update classifiers if I don’t find it the desired bank according to his BIC.

How to do this step by step below.

1. Go to the "Administration" section and select "Maintenance" () in the action panel:

2. In the window that opens, find and select “Routine and background tasks”: