Choosing a server for 1C

When our specialists need to make a configuration choice for a 1C server, the first thing they ask is how many users will work with 1C in the company and what set of services are planned to be used, what will be the tasks of a 1C server, who will administer 1C servers and how. We are starting from this information when creating a 1C server.

1C server requirements

In the hardware structure of the 1C server, the characteristics of the processor, RAM, disk subsystem and network interfaces will be important to us.

It is necessary that they ensure stable and sufficiently productive operation of the following components:

operating system;
database server (most often it is MS SQL Server);
server side 1C (not for all cases, since a small company for 2-10 users can work with 1C in file mode);
user experience in Remote Desktop mode;
work of remote users through a thin client or web client.

The choice of processor for 1C server

The optimal number of processor cores is usually calculated on the basis that 1-2 cores should be reserved for the OS, 1-2 cores for the operation of the SQL database, 1 more for the application server and approximately 1 core for every 8-10 simultaneous user sessions (so that users do not complain later that the 1C server slows down).

Please note that the speed of request processing depends not so much on the number of cores as on the processor clock frequency, and the number of cores affects stability more with a large number of users and simultaneous tasks from them

How much memory does 1C server need

If you need a server for 1C for 100 or more users, we recommend you deploy a cluster of at least two physical 1C servers.

The size of the necessary RAM, we propose to consider, based on such indicators:

•  2 GB required for the operating system
•  at least 2 GB for the operation of the MS SQL Server cache, and it is better that this value is 20-30% of the real database size - this will provide comfortable work for users with it
•  1 - 4 GB for 1C application server
•  100 - 250 Mb will require one user terminal session, depending on the set of functions of the 1C server, the configuration used

It is better to purchase RAM with a margin - this is one of the most important factors for the high performance of a 1C server and at the same time it is now one of the cheapest components. If there is not enough memory on the 1C Enterprise server, this will be very noticeable during operation, therefore, when the question is which 1C server to choose, always pay attention to ensure that it has sufficient RAM.

When choosing which server is needed for 1C, it should be remembered that while users are working with it, many data read and write operations per second will be performed. This parameter - with what speed the hard drive allows to process data - is also one of the key for 1C server performance.

•  It does not matter which server you create for 1C, we do not recommend using single disks in servers - it is advisable to organize them into RAID arrays (RAID 10 for large or RAID 1 for small databases), where the database tables will be located.
•  We recommend placing index files on a separate SSD for faster access to them
•  TempDB - 1-2 (RAID 1) SSD.
•  Place OS and user data on RAID 1 from SSD / HDD.
•  Allocate a separate logical drive from the array or a physical SSD drive under the log files.
•  If possible, use a hardware controller - we had to see situations when a powerful and expensive server slowed down due to insufficient controller performance.

Reliability:

Database server reliability can be achieved by:

•  Regular backups (system, databases, etc.)
•  Uses of RAID 1 and higher for all disk drives.
•  Use of accessories with a replacement guarantee. In remote regions, the use of spare parts.
•  The safest and most expensive option is to use a bunch of two servers working in cluster mode.

In the case of using dedicated servers in data centers, the data center is responsible for reliability.

Organization of user work:

There are 2 possible schemes: a terminal server and work in a thin client from their working machines. Consider the pros / cons:

Terminal server:

Pros:

Ability to securely connect from anywhere in the world.
If users work in various information databases, you can save on 1C licenses by installing licenses on the terminal server (as single-user), and not on the 1C server.
Ease of administration. It is much easier to perform operations such as updating the platform, clearing the user cache, connecting to a user session (with a screen shot), administering the list of databases, etc.
Monitoring system performance, it’s easier to look for bottlenecks.

Work from your place:

Minuses:

User computers must meet the minimum system requirements.
Additional traffic within the network.
In general, 1C licenses are issued for each connection to the infobase.
There is no way to connect to infobases outside the local network (a solution is to organize WEB access to infobases)
There are some difficulties with administration, such operations as updating the platform, clearing the user cache, administering the list of databases, etc. are more difficult.
Difficult user support. To access the user session, special tools are needed (TeamViewer, RAdmin, LiteManager, etc.)

A combined case is also possible when some users work from a terminal server, some from their workstations.

Conclusion

You should not try to save money by using a user computer for the 1C server (as is often done in small companies) - the user hardware is much less reliable and fault-tolerant than a similar server one. Do not risk the accounting system of your company. If the purchase of suitable hardware does not fit your budget, you should probably consider deploying 1C in the cloud.

If it is difficult for you to find out which server to choose for 1C, how to make a 1C server, because you have not encountered this task before, you can always contact us. Experienced technical specialists will help you design, buy, install and configure a server suitable for you for 1C.