You are viewing limited content. For full access, please sign in.

Question

Question

Splitting up server roles

asked on December 9, 2019

I have two Windows servers with Laserfiche applications installed on them: one internal with all apps (SQL Server, Directory Server, DCC, Forms, Workflow)  and one public facing forms server.

To improve performance and scalability, I want to move some apps off of the internal server. I think ultimately I want to split the roles as much as possible as per best practices. Because of the complexity of doing that all at once, is there a priority of roles to start with to install on their own server? 

0 0

Replies

replied on December 9, 2019

SQL Server might be the best to isolate first, since all the active data is stored there and it is queried often. This means you want to consistently dedicate enough RAM so that the hard disk is never used on a query (ideally). Queries can also be CPU intensive.

For web services it depends on how they are used and why you would want to isolate them.


You do not need to spin up more operating systems in order to isolate these services though, you can simply use affinity to designate specific cores and designate chunks of memory to each service. This is MORE efficient than adding another host which requires MORE resources. Both SQL Server supports CPU affinity and Memory Limits, IIS supports "per application" cpu affinity and memory limits. The way memory is dedicated is simply by making sure the total of all limits set is not greater than the available memory.

2 0
replied on December 9, 2019

Ok thanks. Because the LF SQL Server is hosting other databases, I could 'isolate SQL' by moving everything else Laserfiche related off of that server. 

0 0
replied on December 9, 2019

No need, just install a second SQL instance. Each instance allows you to manage the hardware dedicated to that instance. Another instance also shares the same SQL license, so no need to buy more. I think you can have up to 12 per license.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.