I'm writing an application which may write tens of thousands of blobs simultaneously. Each blob will be around 1k.
In initial testing, it appears that H2 writes each blob using a separate thread. I doubt that approach will scale in my use case. While I could adjust the design of my app to accommodate this behavior, I'd prefer some direct control over it such as providing my own thread pool or something else. Does BINARY / VARBINARY have this same behavior? Maybe that would map better to my use case. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/2oJVTsrQglYJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
