R
Rob Mylett
Guest
We have configured new Linux hosts to run in a VMWare environment. We have 1 VM running on a single ESX host. The HP Linux server has 4 sockets with 10 cores/socket for a total of 40 CPU's. The test is to connect to a database running on the new server, remotely using (-db, -H, -S) to the same database in a loop the connection should be made in less than 50 milliseconds. All that is being done, is to do a native Progress ABL connect -db (dbname) -H (IP Address) and -S (port number), and record the elapsed time before and after the connection. When we configure the host to run with 1 socket and 8 CPU's, for a total of 8 cores, the database acts normal and most connections are within 25-35 milliseconds. When we change the configuration to 4 sockets and 8 CPU's, for a total of 32, the same exact causes the connection to pause, for various times, from 8 seconds to sometimes over 2 minutes. Working with VMWare and Progress on this issue, it was determined that we try a different network driver. We were using vmxnet3, and tried using e1000. The e1000 driver worked, and eliminated the pause completely. We were contacted by Progress that we should be using vmxnet3, and VMWare is stating that e1000 driver is old and should be using vmxnet3 as well. So my question, has anyone run into this issue? Is anyone running with VMWare, with vmxnet3 network driver, over multiple sockets? Has anyone tested doing a remote database connection to determine if there have been any pauses in connecting? Thanks.
Continue reading...
Continue reading...