#1  
Old 26th July 2018, 01:29 AM
jhoehne jhoehne is offline
Junior Member
 
Join Date: Apr 2018
Posts: 10
Default Connecting speed

Hello,

connecting to a database on the same machine via TCP/IP takes approx. 3 seconds. Is this a normal connection time?

I made a small test program, only nxRemoteServerEngine, nxWinsockTransport, nxSession, nxDatabase and nxQuery (but didn't open the Query, just set nxDatabase.Active := true). This took 3 seconds on a VM on a Xeon-1240v3 with a Samsung SSD as system and data drive.

--
Joachim

P.S.: if I close the connection and re-open, it's instantly.
  #2  
Old 26th July 2018, 01:40 AM
Rodrigo G?mez
 
Posts: n/a
Default Re: Connecting speed

How are you setting the servername? Is it an IP or a computer name?
Maybe the problem is the DNS server/settings.

HTH

--
Rodrigo G?mez [NDX]
M?xico, GMT-6
  #3  
Old 26th July 2018, 11:04 AM
Eivind Bakkestuen [NDD]
 
Posts: n/a
Default Re: Connecting speed

> connecting to a database on the same machine via TCP/IP takes approx.
> 3 seconds. Is this a normal connection time?
>
> I made a small test program, only nxRemoteServerEngine,
> nxWinsockTransport, nxSession, nxDatabase and nxQuery (but didn't open
> the Query, just set nxDatabase.Active := true). This took 3 seconds
> on a VM on a Xeon-1240v3 with a Samsung SSD as system and data drive.


If you are relying on the automatic broadcast discovery of the server,
instead of setting dns/IP address directly, then yes, the xeons and
SSDs won't make any difference.

You can adjust timeout properties on the transport, or use the actual
name/IP.

--
Eivind Bakkestuen [NDD]
  #4  
Old 26th July 2018, 11:22 PM
jhoehne jhoehne is offline
Junior Member
 
Join Date: Apr 2018
Posts: 10
Default

Quote:
Originally Posted by Eivind Bakkestuen [NDD] View Post
> connecting to a database on the same machine via TCP/IP takes approx.
> 3 seconds. Is this a normal connection time?
>
> I made a small test program, only nxRemoteServerEngine,
> nxWinsockTransport, nxSession, nxDatabase and nxQuery (but didn't open
> the Query, just set nxDatabase.Active := true). This took 3 seconds
> on a VM on a Xeon-1240v3 with a Samsung SSD as system and data drive.


If you are relying on the automatic broadcast discovery of the server,
instead of setting dns/IP address directly, then yes, the xeons and
SSDs won't make any difference.

You can adjust timeout properties on the transport, or use the actual
name/IP.

--
Eivind Bakkestuen [NDD]
Ah! I've set only "ServerNameDesigntime" and thought this will be used at runtime too if I leave ""ServerNameRuntime" blank.
With "ServerNameRuntime" set to "NexusDB@127.0.0.1" too it takes only 22 msec.

Thank you!


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Best practices when connecting to a server Scott Slater nexusdb.public.discussions 9 16th June 2007 12:54 AM
Connecting to my server... =?ISO-8859-1?Q?Cl=E9mentDoss?= nexusdb.public.support 3 21st October 2006 10:12 AM
Connecting to right server Anders Gustavsson nexusdb.public.support 1 17th February 2006 07:04 AM
Connecting in DLL Luke Johnston nexusdb.public.support 2 24th January 2006 12:57 PM
V2 speed vs V1.08 speed over ADSL/SDSL and HDSL connections Bert Moorthaemer nexusdb.public.support 20 2nd May 2005 06:31 PM


All times are GMT +11. The time now is 11:44 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.