You’re using ordered set which is relatively slow compared to other types. Could you use regular set? Also if the table is accessed from other processes, provide the read_concurrency: true option (but in your case you don’t need write_concurrency, b/c the table is protected, so it’s written to from a single process.
You already answered it yourself:
So basically, measure twice, cut once ![]()
Can you elaborate why? I’d be surprised if that solution would be significantly faster than ETS, if faster at all, b/c I think (but not completely sure) that the same limitations apply (data still has to be copied in/out).






















