The recommendations for laserfiche Web are really high (3.0Ghz) for server grade processors. Does that take into account socket count? We are in the process of buying new hardware to host our virtual machines including the laserfiche machines and the cost for servers with xeon processors with enough cores to handle vm density but the speed to meet laserfiche recommendations for web client get really high really quick. Can someone shed some light on why 3Ghz and if core count and xeon level processors are taken into account.
Question
Question
Replies
You're right that clock speed is much less of an objective measuring stick than it used to be, so that complicates any recommendations we give. Additionally, variations between repositories and usage patterns will have a huge impact on the resources required, and that's before you consider the several orders of magnitude variation in user count between organizations. Some workloads would benefit from more cores, others from faster ones - and that's assuming that your workload is running into any kind of ceiling.
So definitely take those numbers with a grain of salt. If this is a new installation, you can start with the hardware you have available and see if it's sufficient.
Sorry for the delay. I assumed I'd get an email if someone commented. Thank you for the information provided. We ended up buying new hardware with some pretty impressive specs. Unfortunately many of the web based services for laserfiche are still pretty slow. The physical CPU's are Intel Xeon Gold 6128 CPU's at 3.4GHz. 2 sockets 6 cores per socket. These are really fast server class CPU's. The actual laserfiche virtual machine that houses LF Web and LF Forms has 6 vCPUs and 16GB of RAM. Worflow, import agent and SQL are all housed on different servers. We have 55 users. I'd expect much better performance given the hardware.
The hardware specs all seem more than adequate. Many user interactions require a round-trip through all the tiers - web, LFS, SQL - so network latency is an important factor and can be impacted by firewalls, proxies, etc, and that's the next place I'd investigate. Your Solution Provider might be able to offer some suggestions also.