There is a significant difference in the time required for unit testing of different versions of Rocksdb on Mac OS
Opened this issue · 1 comments
Note: Please use Issues only for bug reports. For questions, discussions, feature requests, etc. post to dev group: https://groups.google.com/forum/#!forum/rocksdb or https://www.facebook.com/groups/rocksdb.dev
Expected behavior
Regardless of the version of Rocksdb, the overall time required for unit testing should be similar, or is there any configuration that can shorten the time?
Actual behavior
When I was conducting unit testing on Mac OS using different versions of Rocksdb, I found that the overall CI time for version 7.7.3 was much longer than that for version 5.15.10
Steps to reproduce the behavior
@Test
public void testOpen() throws RocksDBException {
for (int i = 0; i < 60; i++) {
long start = System.currentTimeMillis();
try(RocksDB db = RocksDB.open("test-open-" + i)) {
System.out.println("RocksDB.open() cost:" + (System.currentTimeMillis() - start));
} finally {
RocksDB.destroyDB("test-open-" +i, new Options());
}
}
}
View database loading logs
Version 7.7.3
RocksDB.open() cost:194
RocksDB.open() cost:195
RocksDB.open() cost:199
RocksDB.open() cost:198
RocksDB.open() cost:177
RocksDB.open() cost:199
RocksDB.open() cost:198
RocksDB.open() cost:200
RocksDB.open() cost:198
RocksDB.open() cost:196
RocksDB.open() cost:195
RocksDB.open() cost:194
RocksDB.open() cost:197
RocksDB.open() cost:192
RocksDB.open() cost:195
RocksDB.open() cost:197
RocksDB.open() cost:201
Version 5.15.10
RocksDB.open() cost:2
RocksDB.open() cost:2
RocksDB.open() cost:2
RocksDB.open() cost:2
RocksDB.open() cost:2
RocksDB.open() cost:3
RocksDB.open() cost:3
RocksDB.open() cost:2
RocksDB.open() cost:2
RocksDB.open() cost:2
RocksDB.open() cost:3
RocksDB.open() cost:3
RocksDB.open() cost:2
RocksDB.open() cost:3
RocksDB.open() cost:3
RocksDB.open() cost:2
RocksDB.open() cost:3
RocksDB.open() cost:3
RocksDB.open() cost:3
RocksDB.open() cost:3
My project has many single test cases using Rocksdb, and I hope that upgrading the version can shorten the time. Can you tell me what to do?
Hi @GuipaiQigong111 this looks like you are encountering the same issue as #11035 - unfortunately not an easy fix;