Best Practices on ArcGIS Server Feature Service Performance

2010
4
10-09-2015 08:34 AM
JeremyBridges
Occasional Contributor

We've seen some odd behavior with ArcGIS Server at a client's site and at our shop. We've set up a Server to mainly host one service. We don't tend to hit it very hard. After running it for a while (weeks), we notice that it is maintaining 100+ connections to the database. Also, after restarting the server and letting that service start up, but before we run any queries on the service, it has opened 4 connections to the database.

At our client's site, the behavior is more pronounced (and perhaps unrelated). The same service crashes their Server after running there for a while (with out of memory errors in the log). They have been able to stabilize things by setting the min and max SOC process counts to the same number (2). The server hasn't crashed on them for a couple weeks since they made this change. We're thinking that they may be related because if lots of connections are being held open it could cause the server to run out of memory.

Is this expected behavior? Is there some tuning steps we can take to lessen this? Perhaps we need to change how we query it?

0 Kudos
4 Replies
JakeSkinner
Esri Esteemed Contributor

Hi Jeremy,

It sounds like there may be an issue with your database removing connections.  A service should not spawn more connections than the max instances.  If a service reaches it's max instances, and then becomes idle, the instances will return to the min instances after the 'maximum time an idle instance can be kept running' time is reached.  Connections should then be removed from the database.

What RDBMS are you using (i.e. SQL Server, Oracle)?

How are you connecting to the database (i.e. direct connection, SDE service connection)?

0 Kudos
JeremyBridges
Occasional Contributor

SQL Server 2014, Direct connection.

0 Kudos
JakeSkinner
Esri Esteemed Contributor

Are you using ArcGIS 10.3.1?

0 Kudos
JeremyBridges
Occasional Contributor

Our client and us are using 10.3. They are upgrading to 10.3.1 within a day or two.

0 Kudos