Skip to content

Performance Results

liangjh edited this page Sep 1, 2012 · 3 revisions

Introduction Performance testing on the Casper Datasets Library. Its important to note that full table scans on caches of such large cardinality still perform relatively well. Searches against columns that have been configured as either primary keys or columns perform far better.

Performance Results CASPER Datasets has been proven to scale very well. Here are the results of two particular tests, among many that have been run. The following tests were performed on a database table with over 350,000 rows.

TEST A :: CACHE CARDINALITY :: 15764

Test 1 :: Filter, PK search

Retrieval via match on primary key field...

Filter performance: 31 ms.

Test 2 :: Filter, Regex search 1

Retrieval via non-indexed field match. Performing full table scan...

Filter performance: 16 ms.

Number matches: 73

Test 3 :: Filter, Regex search 2

Retrieval via non-indexed field match. Performing full table scan...

Filter performance: 16 ms.

Number matches: 1289

TEST B :: CACHE CARDINALITY :: 370103

Test 1 :: Filter, PK search

Retrieval via match on primary key field...

Filter performance: 31 ms.

Test 2 :: Filter, Regex search 1

Retrieval via non-indexed field match. Performing full table scan...

Filter performance: 265 ms.

Number matches: 73

Test 3 :: Filter, Regex search 2

Retrieval via non-indexed field match. Performing full table scan...

Filter performance: 329 ms.

Number matches: 16447