db_processes_per_client - for Config DB Server?

[JTL]

All,

what is a recommended value for this in a dbserver.conf file?

We have a large environment...

[René]

Hi timetex,

The recommended value is 1. Based on the note in the documentation Genesys doesn't recommend changing that value unless instructed by Genesys TechSupport or documentation to some Genesys solution.

I don't know what you mean by "large environment" but you can contact Genesys TechSupport and ask them.

René

[JTL]

Cool, thanks...

[guest01]

We have it set to 5 because we are using Oracle. We did several stress tests (a lot of DNs being deleted and added while agents are being modified using SQL Server, and found no difference. Oracle was a bit different. We found changes to DB to take place at much lower pace during heavy config server loads. This means that it is possible for config server to crash before updating config db. Adding number of processes to 5 significantly sped up the speed with which data entered into config server was stored into DB.

And, no, we did not ask Genesys 

[JTL]

[quote author=guest01 link=topic=2416.msg9075#msg9075 date=1187250072]

We have it set to 5 because we are using Oracle. We did several stress tests (a lot of DNs being deleted and added while agents are being modified using SQL Server, and found no difference. Oracle was a bit different. We found changes to DB to take place at much lower pace during heavy config server loads. This means that it is possible for config server to crash before updating config db. Adding number of processes to 5 significantly sped up the speed with which data entered into config server was stored into DB.

And, no, we did not ask Genesys 



[/quote]

That was precisely my thinking...

I've raised a ticket with Genesys to ask their opinion... was just upgrading to v7.5 DB Server and happened to notice, and couldn't remember why it was limited to 1.

[catanirex]

Hi, I found this in the pdf's:


Framework 7.5 Deployment Guide’, Appendix B - Troubleshooting DB Server
Question:
Why does DB Server seem to be losing 50% or more of all data writes?
Answer:
To date, only Universal Routing Server (Interaction Router) is capable of
handling multiple database processes simultaneously; DB Server client (for
example, Call Concentrator) can only handle one process. Therefore, you must
set the DB Server option dbprocesses_per_client to 1.


See documentation for a particular client application to verify whether
that application supports the Multiple Processes mode. If unsure of the
appropriate number, set this option to 1. Increasing the value up to 4 increases
performance; more than 4 does not increase performance.