Answer the question
In order to leave comments, you need to log in
What is the priority for 1s?
We have a terminal server under win2008 (desktop machine, i7, 4 Gb of RAM - a fairly simple machine for 5-6 users), users use 1s-Rarus, file database, located on the same server.
1C is terribly stupid, especially at startup and when something is being formed.
Transferred the database to another machine with raid 0 - test the speed.
And the growth was not a gram, they were specially measured: the calculation ended in a second (something was formed).
What, it turns out that the speed of exchange with the screw is far from the most important parameter for 1C?
Then what is critical for 1C?
Answer the question
In order to leave comments, you need to log in
It is necessary to start with monitoring resources, and not mindlessly transfer to different raids, increase OP, etc.
1. Add RAM (8, better 16 GB)
2. Buy a 128 ssd, split into 2 disks on 1 disk system (do not forget to make an image), on the 2nd 1C.
3. Buy a regular screw, such as WD Green. Daily backups are made from a disk with 1C.
With such a system, it should work fine.
the simplest thing is to open the task manager and look at the load on the processor and memory. If there is not enough memory and everything gets into the swap, then we put more memory.
If the processor is not enough, we change the percentage to a faster one, I feel that 1s uses only one core to generate a report.
then you need to monitor the screws using the perfmon utility,
where did you get the idea that your raid0 will be faster on random reading, I don’t know. take one ssd and drive it.
No super powerful server will save you from shitty code, 1C is not so slow if you prepare it correctly, the configuration is written correctly, find a really good programmer who will find the bottlenecks in your configuration and suggest what and how to improve. 5GB is not such a big base to slow down a lot.
In principle, the file mode is faster than SQL, but on a small number of users < 5.
If the database is file and about 10 are actively working, then there will be any brakes, even on a 1.5GB database.
Those. here unequivocally on an application server+SQL. You can use MS, you can use free postgres and DB2, but they are 20-30 percent slower than MS.
In terms of hardware, memory and disk are usually critical. For a disk, a cool version of SSD screws with a mirror (only a mirror is required, otherwise there are almost no statistics on reliability)
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question