Need test 1s for performance. Are there any?

Question

System administration

After the transfer of 1s to the 8.3.6. platform, major brakes began at startup (about a minute the deployment of a thin client) and samples and other typical actions are made very slowly in 1s itself. The base is about three gigs with the file version. It lies in network storage on a gigabit port with a return speed of up to 40 MB per second. 7 people work with the base. Yes, and then three in reading mode. Are there scripts for 1s to create a typical load on a given base and with a report output?

Answer 1

Yes. There are such tests.
Start with the official documentation - Conducting Load Testing .
Next is the most popular Gilev test .
There are a dozen testing options on Infostart .
And just googling gives a lot of links to alternative sources.

Answer 2

7 people is a lot.
Translate 1C to SQL will be easier.
I advise you to do it on Centos 6.6 + PostgreSQL.
You'll have to get confused and read about the Postgresql setup.
Your brakes are due to blockages.

Answer 3

In the file version, not a thin client is launched on each computer, but the program (platform) itself.
I tried it - on a terminal server with i5 and 8G 1C 8.2.19.116 starts in 2-3 seconds.
Why was it necessary to switch to "8.3.6.something"? revert back to 8.2 or 8.3. 5 .something, if it worked fine before.
Or global changes - transition to the terminal or SQL.

Answer 4

If the configuration is on managed forms, use a web server (in some cases, the speed increase is noticeable to the naked eye).
If not, then go to SQL.

Answer 5

And what, 8.2 did not slow down in the file version?
We have only three users and slows down. True, the base of gigs is 10.
It's either a terminal or a database, only they decide.

Answer 6

How to unload 1s:
1. Deploy the server for 1s. This is implemented in my office, so the server is on windows, and the database is on ubuntu + postgere. Why the server itself is on win and not on Linux, I’ll explain before the appearance of the server it was 1s file year 2 and all processing used com objects on the server side, and on Linux there is no support for the com object. Total = 10 users per day, constant reporting, a large number of processing - everything works well. (Computer on win, i5 + 16GB) on the database (pentium cpu g3420 + 8GB). Pretty modest iron but got rid of all the lags.
Cons:
- Price. The cost of a license for a 1c server + additional hardware.
Pros:
Speed.
2. Use ssd hard drives + raid 1. Those on the PC where the file version is stored buy three SSD drives, 64 GB each is enough. 1 for the OS and makes RAID 1 (mirror) from the other two.
Pros:
Speed ​​increase
No need to buy a license for a 1s server.
Cons: SSDs with a load of 1s will live no more than 3 years.