Bert

hey @metalmatze , following up from your comments on #88. I have this as draft because I had a few outstanding work items: 1. The current code can call the...

@brancz the changes discussed in the comments above have been made. Would you mind reviewing again?

Very cool thanks nice work! @thorfour @metalmatze

Hey @brancz I agree volcano seems like a good fit. To add parallelization to articdb, I think we could add an implementation of the exchange operator described in the paper....

Thanks @brancz, I'll move forward with this. I'll get the code cleaned up, add tests & error handling and do some profiling to verify if this approach improves performance and...

@brancz @metalmatze we've managed to get a good performance boost from this parallelism. I wrote a benchmark program (see below) and found that this is about 50% faster with the...

here is a document with some more of my notes https://docs.google.com/document/d/1-9jX8XafLP3m5hLShSRh1hoMAEKrQTzqS0og2JCOlXg/edit#heading=h.vf1o5lbbldn6

@jkaflik I will check w/ otelsql maintainers and follow up. Do you think it makes sense though to implement ConnBeginTx as driver.Conn's `Begin` method is deprecated? https://pkg.go.dev/database/sql/driver#Conn

We could experiment by removing the `Begin` function. I'm not sure if there are other reasons to keep it around for backwards compatibility? Also, it looks like `otelsql` will begin...

We also have some use cases where we need to check the metric_type. Agreed, would be nice to have a stable way of getting it.