Have a terminal server under win2008 (desktop machine, i7 processor, 4 Gb of RAM — a fairly simple machine for 5-6 users), the users of 1C-Rarus, the database file is located on the same server.
1C awfully stupid, especially when you start and when something is formed.
Moved database to another machine with raid 0 to test the speed.
And gain a single gram, especially measured: the second ended in a settlement (something formed).
That, it turns out that the exchange rate of the screw is not the most important parameter for 1C?
diego.Thompson38 answered on October 8th 19 at 03:32
We should start with the monitoring of resources and not mindlessly carry on different raid, increase OP, etc.
Roel.Hauck answered on October 8th 19 at 03:34
Go to the client-server version of 1C.
Freida_Lehner answered on October 8th 19 at 03:36
Curve code does not help any server performance
nicole.Parker answered on October 8th 19 at 03:38
1) Put the server 1C.
2) Rewrite the bottlenecks.
Kelsi_Stoltenberg answered on October 8th 19 at 03:40
1. Add RAM (8, better 16 GB)
2. Buy SSD 128, split into 2 discs on 1 disc system (not to forget to make the image), the 2nd 1C.
3. Bought a conventional screw, such as WD Green. From the disc 1C being made daily backups.
Such a system should work just fine.
Eulalia22 answered on October 8th 19 at 03:42
the simplest open task Manager and view CPU usage and memory. If memory is not enough and everything in the swap then put the memory still.
If percent is not enough to change the percent faster, I feel 1C uses only one core to generate the report.
further it is necessary to monitor the screws using perfmon utility
where did you get your рейд0 will be faster on randomly reading I don't know. take one SSD and drive on it.
kaia_Jaskolski answered on October 8th 19 at 03:44
No super powerful server will not save you from bad code, 1S not so slow if it correctly to prepare the configuration is written correctly, find a really good programmer, who will find bottlenecks in your configuration and will propose what and how you can improve. 5GB is not so much the base, to very slow.
Delbert_Bauch answered on October 8th 19 at 03:46
In principle, the file mode faster SQL-tion, but a small percentage of users < 5.
If the DB file and are actively working about 10 — the brakes certainly will be, even on the basis of 1.5 GB.
Ie is clearly on the application server+SQL. You can use MS you free postgres and DB2, but they are slower MS 20-30 percent.
On gland — like Pavlo critical memory and disk. To drive a classy version of the SSD screws of the mirror (just be sure to mirror, and then statistics on the reliability of there almost)
erin_Watsica72 answered on October 8th 19 at 03:48
For file 1C top priority time random access to the file!
And ready not to reduce it, on the contrary even.
This tunim caches the file system on the server, and brains moving in the direction of the raptors and SSD :-)
Well, to clean up the grid. A situation where the unmanaged switch, the switch sits and switch whipping, unacceptable!
From personal experience, the old core 2 duo with 4 gigs operatives and a black woodpecker was enough to delight the five bukhov, file 1C.
1C and a file on the RAM-disk, all burning with Napalm...
PS. In General, and SQL server, is also possible and need to know how to cook!