Test report.
1.1Purpose
Test forthe YLink to learn about the performance comparison between local and networkcluster.
1.2limitation
Used forCommunication Between Yllink And Mcobject Only.
1.3Documentdescription
The environmentand test results are listed, besides the screen-shot is attached.
2Local vs network Cluster
From Email：
Mr T: i want to know that the single operator(such as 'insert')transaction's performance difference between the single node mode and thecluster mode(with 4 nodes).
Mr S：What is the platform you’ll be running on(Windows, Linux, 32-bit or 64-bit)?
How fast areyour network components (NIC and router)?
Instead of trying to guess at theperformance, I strongly recommend that one of our technical staff(Bruce/Jack/Gary) work with you to get the ‘cluster_perf’ sample programrunning on your cluster network so that you can measure the performanceempirically.
Bruce：I could have a test underour wifi environment with the example cluster_perf. And I would mark theoverhead for each part(transaction execution on each node, and the networkoverhead accordingly), which may be not optimistic statistics with wifi routerand laptop.
2.1Local Cluster
The testhost is Centos in VMware on mylaptop
The datatransferred is relatively simple:
class Record
{
uint4 key;
hash <key> hkey[20000];
tree <key> tkey;
};
[ly@localhostbin]$ ./cluster_perf 2 0
Socket send buffer size : 0
Socket recv buffer size : 0
Connect timeout : 5000
Connect interval : 200
Keep-alive time : 1000
Keep-alive probes : 5
Socket domain : AF_INET
Window length (intransaction) : 0
Window size (in bytes) : 0
Window timeout : 1
Connection pool factor : 50
This node ID : 0
Number of nodes : 2
Node 127.0.0.1:20000, rank 1
Node 127.0.0.1:20100, rank 1
Insert:
100000objects: 562 milliseconds,(5 microsecs/object)
Hashsearch:
.................... 100000 searches: 113 milliseconds (1microsecs/search)
Treesearch:
....................
100000searches: 285 milliseconds (2 microsecs/search)
Sequential:
..........
100000searches: 100 milliseconds (1 microsecs/search)
Search/delete:
..........
100000objects: 782 milliseconds (7 microsecs/object)
Figure 1: Screen-shoton VM Centos
2.1Network Cluster
OS:linux vs windows
192.168.1.100:window laptop
192.168.1.220:Redhat on the network.
Therouter is wifi using the DLink DIR-618
The datatransferred is relatively simple:
class Record
{
uint4 key;
hash <key> hkey[20000];
tree <key> tkey;
};
c:\McObject\Fusion\eXtremeDB\win32vs2010\target\bin>cluster_perf--nodelist "192.168.1.220:10000; 192.168.1.100:10000" 1>cluster.log
c:\McObject\Fusion\eXtremeDB\win32vs2010\target\bin>typecluster.log
Socket send buffer size : 0
Socket recv buffer size : 0
Connect timeout : 5000
Connect interval : 200
Keep-alive time : 1000
Keep-alive probes : 5
Socket domain : AF_INET
Window length (intransaction) : 0
Window size (in bytes) : 0
Window timeout : 1
Connection pool factor : 50
This node ID : 1
Number of nodes : 2
Node 192.168.1.220:10000, rank 1
Node 192.168.1.100:10000, rank 1
Insert:
100000 objects: 2656 milliseconds,(26microsecs/object)
Hash search:
....................
100000 searches: 141 milliseconds (1microsecs/search)
Tree search:
....................
100000 searches: 359 milliseconds (3microsecs/search)
Sequential:
..........
100000 searches: 94 milliseconds (0microsecs/search)
Search/delete:
100001 objects: 1703 milliseconds (17microsecs/object)
Close database : Successful
Press any key to continue . . .
Figure 2: Networkcluster Win&ReadHat
