Recommended Ignition Architecture

General Discussion
1

Hello everyone, i wanted to ask the community for some recommendations. At my company, we have 3 departments that are sharing one ignition server and one database connected to it. Every department creates and maintain its own projects. We regularly face database performance issues due to a large amount of queries that are being done per second. One of the departments has way more projects, tags and queries than the other two. This department consumes a lot of resources that affects the projects from the other 2 departments. To avoid this, we were planning to have independent ignition servers for each department and create a database for each projects of each department.

Is this a good way of dealing with this problem? has anybody faced something like this?

I'll appreciate any advice.

2

If you're strictly having DB performance issues, you might try splitting out the databases separately first before adding additional Ignition servers. What types of DB transactions are they using? Custom database structures or just historical data? If custom database structures, are proper keys and indices set up on tables? Do you have a DBA that can take a look and make sure best practices are being followed? Is the current database on the same server as Ignition? If so, split the DB server separate from Ignition as a first step and make sure it has enough resources to handle the queries being thrown at it.

1 Like