cruppstahl
Joined 15 years ago
Joined 15 years ago
The reason is that most of the performance is spent in MySQL and not in the key/value store, and then it does not make a big difference if the key/value store is concurrent or not.
In my experience the assumption of "concurrent = fast" is a misconception. Right now upscaledb moves certain operations (i.e. flushing dirty buffers) to the background. It is better to have fast single-threaded code instead of multi-threaded code with a huge locking overhead. A compromise would be to move the lock to the database level (instead of the Environment, which is basically the container for multiple databases), and make sure that there's no shared state between the databases. But that actually does not have that much priority for me because I do not expect to win that much performance.
upscaledb does use transactions. I.e. if you insert a row with a primary and a secondary index then upscaledb inserts two key/value pairs in two databases. All these operations are wrapped in Transactions. They are just not yet supported on SQL level.
Can you elaborate a bit? I have the same problem as the original poster. But founding a company requires IHK membership fees and tax consultant fees. From what I hear this amounts to ~ 1500 €/year.
The rest of your life is starting today. You have a job, a large dating pool and an open future. Visualize your future (it might look like a grey void) and give it a smile and it will no longer look scary (this is something that always works for me!). Then go and find a therapist. She'll help you get rid of the depression, to find motivation in your job and to figure out what to do in the next 40 years.
BTW - I found this article to be encouraging: https://www.nytimes.com/2018/05/04/opinion/sunday/how-to-sur...