SURVEY:SUMMARY:BUILD_DIFFICULTY[not_applicable, reasonable_effort, code_problematic or string] reasonable_effort SURVEY:SUMMARY:CLASSIFICATION[practical,theoretical,hardware] practical SURVEY:SUMMARY:CORRECT_CODE_LOCATION[string] SURVEY:SUMMARY:PUBLISHED_CODE[not_applicable, yes, no] yes SURVEY:SUMMARY:SAME_VERSION[not_applicable, yes, no_but_available, no_and_not_available] yes SURVEY:SUMMARY:STUDY_FOUND_CORRECT_CODE[not_applicable, yes, no] yes SURVEY:AUTHOR1:BUILD_COMMENT[string] Stasis and bLSM are building fine on a clean ubuntu 14.04 machine. It's only the YCSB benchmarking harness that's broken. Everything else builds out of the box, and the system passes tests, etc. So, you can use the code for anything you'd like, other than re-running my experiments.

Thrift and boost are notoriously hard to build, and they're the reaons the benchmarking harness build is failing. Others rely on the code that's not building on a daily basis, and there is certainly help available elsewhere online. In hindsight, I regret relying upon them. Instead of continuing to maintain code with such dependencies, it would be better to reimplement the test harness without third party dependencies.

Either way, I don't think the broken portion of the build would be a serious problem for people trying to compare against this work (compared to the effort associated with performance tuning, experimental setups, etc, etc.) SURVEY:AUTHOR1:BUILD_DIFFICULTY[not_applicable, reasonable_effort, code_problematic or string] reasonable_effort SURVEY:AUTHOR1:BUILD_DIFFICULTY_COMMENT[string] SURVEY:AUTHOR1:CLASSIFICATION[practical,theoretical,hardware] practical SURVEY:AUTHOR1:CLASSIFICATION_COMMENT[string] SURVEY:AUTHOR1:CORRECT_CODE_LOCATION[string] SURVEY:AUTHOR1:PUBLIC_COMMENT[string] SURVEY:AUTHOR1:PUBLISHED_CODE[not_applicable, yes, no] yes SURVEY:AUTHOR1:SAME_VERSION[not_applicable, yes, no_but_available, no_and_not_available] yes SURVEY:AUTHOR1:SAME_VERSION_COMMENT[string] SURVEY:AUTHOR1:STUDY_FOUND_CORRECT_CODE[not_applicable, yes, no] yes