Document layer unexpectedly slow with naive test

I’m evaluating FoundationDB and thought an interesting first step would be to try out the Document Layer. I wrote a simple app talking to MongoDB which loads about 3MB (in text) of data, and does a few queries to make sure the data loaded as expected. It takes less than a second to run in MongoDB. I then pointed the same app at the document layer, it timed out after 660 seconds (which is 11 minutes for those of you counting). Note that both of these are docker containers running on my Mac Pro (the trash can, not the cheese grater). It does make progress through the test, just very slowly.

I’m not even sure where to begin with this. I certainly wasn’t expecting it to be 1000x slower. Is Document Layer intended to be used? Or is it just a demo?

Thanks,
Greg

Okay, I decided to start by profiling. And, of course, it wasn’t where I thought it was. The better MongoDB comparison was < 0.5 seconds and 6.3 seconds for FoundationDB. So it’s only 12x slower. That I can start to figure out what to do with. The timeout was caused by the docker container hanging on shutdown from a deferred task, so it showed up as failing in the test. The container does not respond to signals correctly.

Is anyone working on the Document Layer? It looks like there haven’t been any changes for the docker container in 9 months or so. (And 5 months since any changes).

Thanks,
Greg