Benchmark
From DBSight Full-Text Search Engine/Platform Wiki
| Table of contents |
Benchmark Environment
This benchmark runs on DBSight 1.3.2, which can enable 8 searchers, Jetty server, started by
java -jar start.jar
PIII 450MHz, 256M memory, Index size is 1,084.134MB, not loaded into memory.
| DBSight Version | 1.3.2 |
| DBSight Build | 376 |
| Up Time | 4 minutes 19 seconds (since Fri Sep 29 16:02:22 PDT 2006) |
| OS Name | Linux |
| OS Version | 2.4.19-4GB |
| JVM Vendor | Sun Microsystems Inc. |
| JVM Version | 1.4.1_02-b06 |
| Total Memory | 63.56 MB |
| Free Memory | 18.76 MB |
| Max Memory | 128.00 MB |
| Local Access URL | http://127.0.0.1:8080/dbsight/ |
| Remote Access URL | http://192.168.1.10:8080/dbsight/ |
Benchmark Command and Result
search:/usr/local/apache/bin # ab -n 500 -c 8 http://192.168.1.10:8080/dbsight/search.do?indexName=freedb&q=ABC [1] 16582 This is ApacheBench, Version 1.3c <$Revision: 1.41 $> apache-1.3 Copyright (c) 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Copyright (c) 1998-1999 The Apache Group, http://www.apache.org/ Server Software: Jetty/5.1.4 Server Hostname: 192.168.1.10 Server Port: 8080 Document Path: /dbsight/search.do?indexName=freedb Document Length: 8881 bytes Concurrency Level: 8 Time taken for tests: 81.711 seconds Complete requests: 500 Failed requests: 17 (Connect: 0, Length: 17, Exceptions: 0) Total transferred: 4573004 bytes HTML transferred: 4440622 bytes Requests per second: 6.12 Transfer rate: 55.97 kb/s received Connnection Times (ms) min avg max Connect: 0 0 0 Processing: 503 1299 2240 Total: 503 1299 2240
Benchmark Conclusion
This is not a thorough test, but you can see what you can get with this old machine. With multiple searchers enabled, it can handle 6 search requests relatively easy.
Not So Official Hardware Guide
I had my hands on a Xeon 5160 3GHz, 4G memory, Scsi 100G hard drives with Dell PERC 5/i integrated RAID controller, for indexing. DBSight's multi-threaded indexing scales amazingly fast on multi-core processors. Indexing 2.2 million records, 1.45G data takes about 25 minutes. The memory is not fully used.
However, Intel's Core 2 series can get faster: http://www.gamepc.com/labs/view_content.asp?id=5160vs6800&page=12 This is because Xeon's memory is slower: http://www.gamepc.com/labs/view_content.asp?id=5160vs6800&page=7
DBSight's indexing also needs faster memory. So I guess an Intel Core 2 E6700 could be your best choice.
