Automation tips. Automation tips Reasons for very slow operation of 1s 8

IN lately Users and administrators are increasingly beginning to complain that new 1C configurations developed based on a managed application are slow, in some cases unacceptably slow. It is clear that new configurations contain new functions and capabilities, and therefore are more resource-demanding, but most users do not understand what primarily affects the operation of 1C in file mode. Let's try to correct this gap.

In ours we have already touched on the impact of productivity disk subsystem at the speed of 1C, however this study concerned the local use of the application on a separate PC or terminal server. At the same time, most small implementations involve working with a file database over a network, where one of the user’s PCs is used as a server, or a dedicated file server based on a regular, most often also inexpensive, computer.

A small study of Russian-language 1C resources showed that this question diligently avoids it; if problems arise, it is usually recommended to switch to client-server or terminal mode. It has also become almost generally accepted that configurations on a managed application work much slower than usual. As a rule, the arguments are “iron”: “Accounting 2.0 just flew, and the “troika” barely moved. Of course, there is some truth in these words, so let’s try to figure it out.

Resource consumption, first glance

Before we began this study, we set ourselves two goals: to find out whether managed application-based configurations are actually slower than conventional configurations, and which specific resources have the primary impact on performance.

For testing, we took two virtual machines running Windows Server 2012 R2 and Windows 8.1, respectively, giving them 2 cores of the host Core i5-4670 and 2 GB of RAM, which corresponds to approximately an average office machine. The server was placed on a RAID 0 array of two, and the client was placed on a similar array of general-purpose disks.

As experimental bases, we selected several configurations of Accounting 2.0, release 2.0.64.12 , which was then updated to 3.0.38.52 , all configurations were launched on the platform 8.3.5.1443 .

The first thing that attracts attention is the increased size of the Troika’s information base, which has grown significantly, as well as a much greater appetite for RAM:

We are ready to hear the usual: “why did they add that to this three,” but let’s not rush. Unlike users of client-server versions, which require a more or less qualified administrator, users of file versions rarely think about maintaining databases. Also, employees of specialized companies servicing (read updating) these databases rarely think about this.

Meanwhile, the 1C information base is a full-fledged DBMS of its own format, which also requires maintenance, and for this there is even a tool called Testing and correcting the information base. Perhaps the name played a cruel joke, which somehow implies that this is a tool for troubleshooting problems, but low performance is also a problem, and restructuring and reindexing, along with table compression, are well-known tools for optimizing databases. Shall we check?

After applying the selected actions, the database sharply “lost weight”, becoming even smaller than the “two”, which no one had ever optimized, and RAM consumption also decreased slightly.

Subsequently, after loading new classifiers and directories, creating indexes, etc. the size of the base will increase; in general, the “three” bases are larger than the “two” bases. However, this is not more important, if the second version was content with 150-200 MB of RAM, then the new edition needs half a gigabyte and this value should be taken into account when planning the necessary resources for working with the program.

Net

Network bandwidth is one of the most important parameters for network applications, especially like 1C in file mode, which move significant amounts of data across the network. Most networks of small enterprises are built on the basis of inexpensive 100 Mbit/s equipment, so we began testing by comparing 1C performance indicators in 100 Mbit/s and 1 Gbit/s networks.

What happens when you launch a 1C file database over the network? The client downloads a fairly large amount of information into temporary folders, especially if this is the first, “cold” start. At 100 Mbit/s, we are expected to run into channel width and downloading can take considerable time, in our case about 40 seconds (the cost of dividing the graph is 4 seconds).

The second launch is faster, since some of the data is stored in the cache and remains there until the reboot. Switching to a gigabit network can significantly speed up program loading, both “cold” and “hot”, and the ratio of values ​​is respected. Therefore, we decided to express the result in relative values, taking the most great value each measurement:

As you can see from the graphs, Accounting 2.0 loads at any network speed twice as fast, the transition from 100 Mbit/s to 1 Gbit/s allows you to speed up the download time by four times. There is no difference between the optimized and non-optimized "troika" databases in this mode.

We also checked the influence of network speed on operation in heavy modes, for example, during group transfers. The result is also expressed in relative values:

Here it’s more interesting, the optimized base of the “three” in a 100 Mbit/s network works at the same speed as the “two”, and the non-optimized one shows twice as bad results. On gigabit, the ratios remain the same, the unoptimized “three” is also half as slow as the “two”, and the optimized one lags behind by a third. Also, the transition to 1 Gbit/s allows you to reduce the execution time by three times for edition 2.0 and by half for edition 3.0.

In order to evaluate the impact of network speed on everyday work, we used Performance measurement, performing a sequence of predetermined actions in each database.

Actually, for everyday tasks throughput the network is not a bottleneck, an unoptimized “three” is only 20% slower than a “two”, and after optimization it turns out to be about the same faster - the advantages of working in thin client mode are felt. The transition to 1 Gbit/s does not give the optimized base any advantages, and the unoptimized and the two begin to work faster, showing a small difference between themselves.

From the tests performed, it becomes clear that the network is not a bottleneck for the new configurations, and the managed application runs even faster than usual. You can also recommend switching to 1 Gbit/s if heavy tasks and database loading speed are critical for you; in other cases, new configurations allow you to work effectively even in slow 100 Mbit/s networks.

So why is 1C slow? We'll look into it further.

Server disk subsystem and SSD

In the previous article, we achieved an increase in 1C performance by placing the databases on an SSD. Perhaps the performance of the server's disk subsystem is insufficient? We measured the performance of a disk server during a group run in two databases at once and got a rather optimistic result.

Despite the relatively large number of input/output operations per second (IOPS) - 913, the queue length did not exceed 1.84, which is a very good result for a two-disk array. Based on this, we can make the assumption that a mirror made from ordinary disks will be enough for the normal operation of 8-10 network clients in heavy modes.

So is an SSD needed on a server? The best way to answer this question will be through testing, which we carried out using a similar method, the network connection is 1 Gbit/s everywhere, the result is also expressed in relative values.

Let's start with the loading speed of the database.

It may seem surprising to some, but the SSD on the server does not affect the loading speed of the database. The main limiting factor here, as the previous test showed, is network throughput and client performance.

Let's move on to redoing:

We have already noted above that disk performance is quite sufficient even for working in heavy modes, so the speed of the SSD is also not affected, except for the unoptimized base, which on the SSD has caught up with the optimized one. Actually, this once again confirms that optimization operations organize information in the database, reducing the number of random I/O operations and increasing the speed of access to it.

In everyday tasks the picture is similar:

Only the non-optimized database benefits from the SSD. You, of course, can purchase an SSD, but it would be much better to think about timely maintenance of the database. Also, do not forget about defragmenting the section with infobases on the server.

Client disk subsystem and SSD

We analyzed the influence of SSD on the speed of operation of locally installed 1C in, much of what was said is also true for working in network mode. Indeed, 1C quite actively uses disk resources, including for background and routine tasks. In the figure below you can see how Accounting 3.0 quite actively accesses the disk for about 40 seconds after loading.

But at the same time, you should be aware that for a workstation where active work is carried out with one or two information databases, the performance resources of a regular mass-produced HDD are quite sufficient. Purchasing an SSD can speed up some processes, but you won’t notice a radical acceleration in everyday work, since, for example, downloading will be limited by network bandwidth.

Slow hard drive can slow down some operations, but by itself cannot cause the program to slow down.

RAM

Despite the fact that RAM is now obscenely cheap, many workstations continue to work with the amount of memory that was installed when purchased. This is where the first problems lie in wait. Already based on the fact that the average “troika” requires about 500 MB of memory, we can assume that a total amount of RAM of 1 GB will not be enough to work with the program.

We reduced the system memory to 1 GB and launched two information databases.

At first glance, everything is not so bad, the program has curbed its appetites and fit well into the available memory, but let’s not forget that the need for operational data has not changed, so where did it go? Reset to disk, cache, swap, etc., the essence of this operation is that unnecessary at the moment data is sent from fast RAM, the amount of which is not enough, to slow disk memory.

What will this lead to? Let's see how system resources are used in heavy operations, for example, let's launch a group retransfer in two databases at once. First on a system with 2 GB of RAM:

As we can see, the system actively uses the network to receive data and the processor to process it; disk activity is insignificant; during processing it increases occasionally, but is not a limiting factor.

Now let's reduce the memory to 1 GB:

The situation is changing radically, the main load now falls on the hard drive, the processor and network are idle, waiting for the system to read the necessary data from the disk into memory and send unnecessary data there.

At the same time, even subjective work with two open databases on a system with 1 GB of memory turned out to be extremely uncomfortable; directories and magazines opened with a significant delay and active access to the disk. For example, opening the Sales of goods and services journal took about 20 seconds and was accompanied all this time by high disk activity (highlighted with a red line).

To objectively evaluate the impact of RAM on the performance of configurations based on a managed application, we carried out three measurements: the loading speed of the first database, the loading speed of the second database, and group re-running in one of the databases. Both databases are completely identical and were created by copying the optimized database. The result is expressed in relative units.

The result speaks for itself: if the loading time increases by about a third, which is still quite tolerable, then the time for performing operations in the database increases three times, there is no need to talk about any comfortable work in such conditions. By the way, this is the case when buying an SSD can improve the situation, but it is much easier (and cheaper) to deal with the cause, not the consequences, and just buy the right amount of RAM.

Lack of RAM is the main reason why working with new 1C configurations turns out to be uncomfortable. Configurations with 2 GB of memory on board should be considered minimally suitable. At the same time, keep in mind that in our case, “greenhouse” conditions were created: a clean system, only 1C and the task manager were running. IN real life on a work computer, as a rule, a browser, an office suite are open, an antivirus is running, etc., etc., so proceed from the need for 500 MB per database plus some reserve, so that during heavy operations you do not encounter a lack of memory and a sharp decrease in productivity.

CPU

Without exaggeration, the central processor can be called the heart of the computer, since it is it that ultimately processes all calculations. To evaluate its role, we conducted another set of tests, the same as for RAM, reducing the number of cores available to the virtual machine from two to one, and the test was performed twice with memory amounts of 1 GB and 2 GB.

The result turned out to be quite interesting and unexpected: a more powerful processor quite effectively took on the load when there was a lack of resources, the rest of the time without giving any tangible advantages. 1C Enterprise (in file mode) can hardly be called an application that actively uses processor resources; it is rather undemanding. And in difficult conditions, the processor is burdened not so much by calculating the data of the application itself, but by servicing overhead costs: additional input/output operations, etc.

Conclusions

So, why is 1C slow? First of all, this is a lack of RAM; the main load in this case falls on the hard drive and processor. And if they do not shine with performance, as is usually the case in office configurations, then we get the situation described at the beginning of the article - the “two” worked fine, but the “three” is ungodly slow.

In second place is network performance; a slow 100 Mbit/s channel can become a real bottleneck, but at the same time, the thin client mode is able to maintain a fairly comfortable level of operation even on slow channels.

Then you should pay attention to the disk drive; buying an SSD is unlikely to be a good investment, but replacing the drive with a more modern one would be a good idea. The difference between generations hard drives can be assessed by to the following material: .

And finally the processor. A faster model will certainly not be superfluous, but makes a lot of sense There is no way to increase its performance, unless this PC is used for heavy operations: group processing, heavy reports, closing the month, etc.

We hope this material will help you quickly understand the question “why 1C is slow” and solve it most effectively and without extra costs.

• Tags:

Please enable JavaScript to view the

2. Features of the program. Often, even with optimal settings, 1C works very slowly. Performance drops especially sharply when the number of simultaneously working with the database exceeds 4-5 users.

Who are you in the company?

Solving the problem slow work 1C depends on who you are in the company. If you are a techie, just read on. If you are a director or accountant, follow the special link ↓

Network Bandwidth

As a rule, not one, but several users work with one information base (IS). At the same time, there is a constant exchange of data between the computer on which the 1C client is installed and the computer on which the information security is located. The volume of this data is quite significant. A situation often arises when a local network operating at a speed of 100 Mbit/s, which is the most common speed, simply cannot cope with the load. And again the user complains about the program being slow.

Each of these factors individually already significantly reduces the speed of the program, but the most unpleasant thing is that usually these things add up.

Now let's look at several solutions to the problem of low 1C operating speed and their cost, using the example local network of 10 average computers.

Solution one. Infrastructure modernization

This is perhaps the most obvious solution. Let's calculate its minimum cost.

At a minimum, for each computer we need a 2 GB RAM stick, which costs, on average, 1,500 rubles, network card with support for speed 1 Gbit/s, costs about 700 rubles. Additionally, you will need at least 1 router that supports a speed of 1 Gbit/s, which will cost approximately 4,000 rubles. Total cost - 26,000 rubles for equipment, excluding work.

In principle, the speed can increase significantly, however, now it will no longer be possible to buy inexpensive computers for the office. Besides, this decision not applicable for those who use Wi-Fi or want to work via the Internet - in their case, the network speed can be tens of times lower. The thought arises: “Is it not possible to implement the entire program on one powerful server, so that the user’s computer does not participate in complex calculations, but simply serves to transfer the image?” Then you can work even on very weak computers, even on low-bandwidth networks. Naturally, such solutions exist.

Solution two. Terminal Server

Gained great popularity back in the days of 1C 7. Implemented on the server Windows versions and copes with our task perfectly. However, it has its pitfalls, namely the cost of licenses.

The operating system itself will cost about 40,000 rubles. In addition to this, we will need for everyone who plans to work in 1C a Windows Server CAL license, costing about 1,700 rubles, and a Windows Remote Desktop Services CAL license, which costs about 5,900 rubles.

Having calculated the cost for a network of 10 computers, we end up with 116,000 rubles. only for one license. Add to this the cost of the server itself (at least 40,000 rubles) and the cost of implementation work, however, even without this, the price for licenses turned out to be impressive.

Solution three. Service 1C Enterprise

1C has developed its own solution to this problem, which can significantly increase the speed of the program. But there is a nuance here too.

The fact is that the cost of such a solution ranges from 50,000 to 80,000 rubles, depending on the edition. For a company with up to 15 users it turns out to be quite expensive. Great hopes were placed on the “mini-server 1C enterprise”, which, according to the 1C company, is aimed at small businesses and costs around 10,000 - 15,000 rubles.

However, when it went on sale, this product was a big disappointment. The point is that maximum quantity There were only 5 users with whom the mini-server could be used.

As one 1C programmer wrote on the forum: “It is still not clear why 1C chose exactly 5 connections! The problems only begin with 4 users, but with five it all ends. If you want to connect a sixth person, pay another 50 thousand. We could do at least 10 connections...”

Of course, the mini-server also found its consumer. However, for companies where 5 or more people work with 1C, a simple and inexpensive solution has not appeared.

In addition to the program acceleration methods described above, there is another one that is ideal for the segment of 5 - 15 users, namely web access for 1C in file mode.

Solution four. Web access for 1C in file mode

The principle of operation is as follows: an additional role of a web server is installed on the computer, on which information security is published.

Naturally, this must be either the most powerful computer on the network, or a separate machine dedicated to this role. After that, you can work with 1C in web server mode. All heavy operations will be performed on the server side, and traffic transmitted over the network will be minimized, as will the load on the client’s computer.

Thus, even very weak machines can be used to work in 1C, and network bandwidth does not become critical. Our tests have shown that you can work comfortably through mobile internet on a cheap tablet without experiencing any discomfort.

This option is inferior to the enterprise 1C server in terms of operating speed, but this difference is practically invisible up to 15-20 users. By the way, to implement a web server you can use IIS (for Windows) and Apache (for Linux) and both of these solutions are free!

Despite the obvious advantages, this method optimization of 1C operation has not gained much popularity.

I can’t say for sure, but most likely this is due to two reasons:

• Quite a weak description technical documentation
• Located at the intersection of responsibility of the system administrator and 1C programmer

Usually, when a system administrator is approached with a problem of low speed, he suggests upgrading the infrastructure or a terminal server; if a 1C specialist is contacted, he is offered a 1C enterprise server. So, if in your company, a specialist responsible for infrastructure and a specialist responsible for 1C work “hand in hand,” then you can safely use a solution based on a web server.

Let's speed up 1C. Remotely, quickly and without your participation

We know how to speed up 1Ski without disrupting the customer. We delve into the problem, do our job and leave. If you want the program to just work normally, contact us. We'll figure it out.

Leave a request and receive a free consultation on accelerating the program.

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 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, 1C executed many background jobs. 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 so full list 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.

Disabling routine and background tasks in 1C 8.3

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 amounts cores and different clock frequencies. 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 latest versions 1C on the Administration tab a Performance section has appeared. 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.

Routine and background tasks are processes that run in the background (without displaying or confirming the user) that are necessary to maintain and update certain 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!

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 companies have recently been abandoning the RIB data exchange system in favor of online mode and terminal access, it is worth remembering that during uploading and downloading 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. Exact reasons this fact are not known, but apparently somewhere deep in the 1C platform there are compatibility problems with operating systems and non-Microsoft DBMS. 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 in the background regulatory 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).