summaryrefslogtreecommitdiffstats
path: root/benchmarks
Commit message (Collapse)AuthorAgeFilesLines
...
* Added a dynamic trie benchmarkDouglas Rumbaugh2024-04-151-0/+98
|
* trie_bench: Added static query latencyDouglas Rumbaugh2024-04-111-3/+21
|
* Updated FSTrie benchmark and some minor fixesDouglas B. Rumbaugh2024-03-261-28/+45
|
* Clean up extraneous fileDouglas B. Rumbaugh2024-03-251-0/+0
|
* Updates for build on OpenBSDDouglas B. Rumbaugh2024-03-253-2/+15
| | | | | | | | | Necessary updates to get the codebase building under OpenBSD 7.5 with clang. This is a minimal set of changes to get building to work, which includes disabling several things that aren't directly compatable. More work will be necessary to get full functionality. In particular, Triespline, PGM, and the reference M-tree do not currently build on OpenBSD with clang due to GNU dependencies or other gcc specific features.
* FSTrie testing and debuggingDouglas Rumbaugh2024-03-221-0/+92
|
* Benchmarking tweaksDouglas Rumbaugh2024-03-141-26/+33
|
* Benchmark updatesDouglas Rumbaugh2024-02-2312-447/+583
|
* Updated watermark benchmark to shuffle dataDouglas Rumbaugh2024-02-201-6/+15
|
* Benchmark updatesDouglas Rumbaugh2024-02-093-2/+248
|
* Fixed benchmark memory leakDouglas Rumbaugh2024-02-081-0/+2
|
* Fully realized shard concept interfaceDouglas Rumbaugh2024-02-078-8/+8
|
* Set up tombstone deletes properlyDouglas Rumbaugh2024-02-051-9/+9
|
* updated btree benchmarkDouglas Rumbaugh2024-01-311-0/+4
|
* IRS bench (replication of existing one)Douglas Rumbaugh2024-01-311-0/+125
|
* BTree benchmarkDouglas Rumbaugh2024-01-312-2/+118
|
* Updated throughput bench to use SOSDDouglas Rumbaugh2024-01-312-21/+39
|
* Updated insert query throughput to use IRS queriesDouglas Rumbaugh2024-01-312-110/+8
|
* insert query tput updatesDouglas Rumbaugh2024-01-311-2/+7
|
* Insert throughput benchmarkDouglas Rumbaugh2024-01-312-45/+219
|
* Query/Insert intermix benchmarksDouglas Rumbaugh2024-01-312-38/+153
|
* Temporary thread affinity for reconstructionDouglas Rumbaugh2024-01-311-6/+7
|
* Benchmarking updatesDouglas Rumbaugh2024-01-308-24/+472
|
* Multithreaded Insertion BenchmarkDouglas Rumbaugh2024-01-241-11/+37
|
* WAtermark testing benchmarkDouglas Rumbaugh2024-01-221-0/+53
|
* Adjusted recon_benchmark and properly shutdown FIFOSchedulerDouglas Rumbaugh2024-01-221-12/+24
|
* Benchmarking: updated insert_query_tput to use better rngDouglas Rumbaugh2024-01-221-3/+14
|
* Moved some benchmarks over to range countDouglas Rumbaugh2024-01-222-6/+6
|
* Initial rough-out of internal statistics trackerDouglas Rumbaugh2024-01-191-0/+2
| | | | | | Need to figure out the best way to do the detailed tracking in a concurrent manner. I was thinking just an event log, with parsing routines for extracting statistics. But that'll be pretty slow.
* Benchmarking programsDouglas B. Rumbaugh2024-01-1517-4/+119
|
* Query throughput benchmarkDouglas Rumbaugh2023-12-131-0/+79
|
* insert_tput: minor adjustmentsDouglas Rumbaugh2023-11-161-12/+7
|
* Insertion throughput benchmarkDouglas Rumbaugh2023-11-151-0/+49
|
* Change PGM to range count.Dong Xie2023-07-283-9/+14
|
* PGM-based Point Lookup benchmarksDouglas Rumbaugh2023-07-274-0/+300
|
* UPGM: added epsilon configuration parameterDouglas Rumbaugh2023-07-261-1/+1
|
* Alex warmup via bulkloadingDouglas Rumbaugh2023-07-261-34/+22
|
* Adjusted calculation for index sizeDouglas Rumbaugh2023-07-263-1/+3
|
* Updatable PGM benchmarkDouglas Rumbaugh2023-07-261-0/+213
|
* Alex: updated progress bar code for benchmarkDouglas Rumbaugh2023-07-251-0/+2
|
* KNN Benches: added k as an optional cmdline argumentDouglas Rumbaugh2023-07-252-14/+8
|
* ALEX: Added progress bars backDouglas Rumbaugh2023-07-251-0/+2
|
* ALEX Benchmarking: added benchmark for ALEXDouglas Rumbaugh2023-07-254-235/+463
|
* Benchmarks: mtree and vptree benchmark updatesDouglas Rumbaugh2023-07-254-8/+58
| | | | | | | | | Note: cosine similarity doesn't seem to work for VPTree--I don't think that it is actually a metric, upon further research. At the very least I can't find anyone claiming it is, and I've found several people claiming it isn't. On testing with the Word2Vec data, Euclidean distance works insofar as the M-Tree and VPTree return the same KNN results for test queries, whereas Cosine Similarity does not work.
* M-Tree benchmarksDouglas Rumbaugh2023-07-244-6/+87
|
* Cosine Similarity TypeDouglas Rumbaugh2023-07-241-1/+1
|
* ISAM IRS query bugfixesDouglas Rumbaugh2023-07-241-1/+1
|
* Benchmarking: Added utility functions for VPTree/KNNDouglas Rumbaugh2023-07-232-4/+127
|
* BTree-based baselines for IRS and Range queriesDouglas Rumbaugh2023-07-234-3/+213
|
* Triespline RQ fixesDouglas Rumbaugh2023-07-231-3/+3
|