Asdine El Hrychy

Currently there's no builtin way to do that on v2, that will be available in v3 only. In the meantime, the only workaround i see is by doing it by...

It's because each call to `Save` uses a transaction, which waits for disk synchronization for each object saved. You should save multiple objects using a single transaction. Example: ```go const...

Actually this is more related to how BoltDB synchronizes data on disk, the time spent on Storm functions is an order of magnitude lower than the disk sync time. This...

@prologic It seems that you are using too many indexes. Each index slows down the writes to speed up the reads when querying on that particular field. If you never...

You can use the [`Batch()` option](https://github.com/asdine/storm#batch-mode) Then all the Storm write methods (Save, Update, DeleteStruct, etc.) will use the bolt Batch method. If you only want that for one particular...

It was just an example because Batch is usually used for concurrent writes accross multiple goroutines (ex: webservers, etc.)

Indeed that's terrible, can you share a code snippet ?

> Do multiple writes get "magically" batched together somehow Yes, there are a few mutexes and a timeout that handle all of that automatically. If you want to do concurrency,...

@joonas-fi Could you share a working example of what you wrote with Storm? I'll investigate tonight and see where is the bottleneck

@mvdan @AndersonBargas This library is not maintained these days because I'm putting all or my energy in [another database](https://github.com/genjidb/genji) which solves lots of Storm design issues (no reflection, SQL as...