Acceptable JDBC Latency for LiveCycle?

[Former Community Member]

Hi,

Does anyone have any thoughts/experience on acceptable latency times for LiveCycle?

By this I mean the trip time from the application server LiveCycle is running on to the database server it is using. In paticular I am interested in the user experience when developing processes in Workbench and the performance of the developed processes when invoked.

Thanks in advance.

[JayanKandathil]

Keeping JDBC out of the picture, we have found that you want to keep ping delays between the appserver instance and the DB server to less than 10 milliseconds.

C:\TEMP>ping db.company.com

Pinging db.company.com [192.150.23.6] with 32 bytes of data:
Reply from 192.150.23.6: bytes=32 time=7ms TTL=255
Reply from 192.150.23.6: bytes=32 time=3ms TTL=255
Reply from 192.150.23.6: bytes=32 time=3ms TTL=255
Reply from 192.150.23.6: bytes=32 time=3ms TTL=255

Ping statistics for 192.150.23.6:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 7ms, Average = 4ms

[Former Community Member]

Thanks Jayan

[Former Community Member]

Less than 10 milliseconds in all cases? As in both prouduction and non-production environments?

[JayanKandathil]

Anywhere performance matters.