Hi, Now our event store is almost complete and working quite well on top of OrientDB, thank you!
I'm wondering what the best setup/configuration is for our case. Inserts: - We have a single thread inserting into the database from a message queue - About 500 - 2000 event messages are inserted every second. - It batches the events messages and writes them in batches depending on batch_size or time_box, what ever comes first. - Each event message creates multiple vertexes/edges Queries - Queries are handled directly with the REST API or with exposing a version of the Java SQL-API. - We need to be able to deal with a high number of concurrent queries (most of them are quite simple) The things I'm considering and need help with are: 1. Should we ignore transactions and WAL because of the single threaded inserts? 2. What is the best way to make sure read-locking is not in the way for queries? 3. What configuration would you recommend? Regards, -Stefán -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
