I'm 40, and I enjoy being 40. I feel that I start to understand why things are the way they are, why other people behave like they do, and why I am how I am. I don't go so far to say that i grok everything, but I certainly have a lot of clarity now that I did not have when I was younger. And I have a toolbox of things that help me when I am not sure about me, about my life etc.
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.
I ran sysbench benchmarks with 30 concurrent connections. The performance gap between InnoDB and upscaledb shrank a bit, but not much.
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.
30 concurrent connections is a very low number, compared to uses of MySQL/InnoDB at real scale. What happens at higher numbers?
I am not arguing that "concurrent = fast". My point is real systems have a higher level of concurrency as a baseline.
InnoDB supports granular concurrent access because real workloads need this. Systems that have poor stories around concurrency -- MyISAM, Redis, pre-WiredTiger MongoDB -- definitely hit real scalability issues under high-volume workloads.
It's ok! The example storage engine could implement more functionality, just to demonstrate i.e. how rows are serialized/deserialized etc. The test suite was very helpful.
Not necessarily. I ran sysbench with InnoDB and manually switched off transactions, and it was a lot slower. I don't know why - didn't look into it.
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.
In InnoDB everything is a transaction. If you do not begin/commit then each statement will be its own transaction.
Batching a group of statements together in a small transaction is usually better because it reduces log flushing. ACID only needs to be guaranteed on commit. Similarly, applying transactions in parallel is faster because of group commit.
Ulp. The whole point of the InnoDB engine is that it supports atomic transactions, even over crashes. If you want an unsafe table, there's the ISAM engine, which is faster.
What does "100% compatible to InnoDB" mean here? It's not functionally compatible and it's not disk-file-format compatible.
If that's your definition of atomicity - yes, upscaledb offers atomic operations. If you define atomicity as the "A" in "ACID" then no - BEGIN/COMMIT wrappers are not yet available. Work in progress!
"Found a small company (UG) with 500EUR capital to hold rights on the site if you want to further professionalize this project."
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.
If you create a legal entitiy you will have to pay taxes / IHK (depending on your annual profit) and some tax consultant fees.
But in my eyes the benefit overweights:
- all your business expenses are kept in a professional setting and don't screw with your personal finances
- you will have a separate bank account
- you have a legal entity you can later sell to a real business
- you can use leftover money to (re-)invest into nearby business areas
- you have limited liability (and you can buy proper insurances for your risky business activities!!)
Your local IHK will be happy to guide you through this process.
I also started off as a sole proprietor and moved up the food chain through UG to GmbH(s), and there is so much you will learn during this process. I think every entrepreneur should have experience with local trade laws and taxes, so in my eyes you can't start early enough.
I was thinking in the direction of a limited in the UK, having read that this is the easiest way. Do you have an opinion on that?
I'm a german living in France, the tax situation is already difficult enough, but yeah – I also think it is a good idea to separate any project income and costs from my personal finances
I strongly advise you against forming a limited in the UK. The setup cost might be low but if something unusual happens the fees for expert advice will eat you alive. Furthermore UK Ltd has a very bad reputation in mainland EU because they are used by many people who aren't allowed to form companies in they home countries (e.g. Germany) any more due to previous bancruptcies.
If you do it out of tax reasons and you are willing to take the risk of not being able to do any administrative "things" by going to a local government agency in the town where you live, then form an entity outside of EU for example in singapore.
Again, I'd suggest you start your first steps in business locally where you can talk to actual people. There are a lot of services available that can help you out in person.
Also, the German tax office will look at your UK registered company and your dividend payments and artificially lowered salary, and your German tax domicile, then tax you after the fact directly as if no company existed. Single ownership UK Ltd companies are a black flag to the Finanzamt.
My best advice is to walk into the local Finanzamt and speak to someone. I've always found them to be knowledgeable, courteous and genuinely interested in helping. Explain to them your goals (minimising tax liability / indemnity / etc) and they will advise you where they can (for free).
Don't do offshore. It's just a premature optimization. It also does not actually save you money unless you're leaving it outside the country. If you want to spend it in France or Germany, you have to pay taxes on it anyway.
If you ever need a credit or want to sell to businesses, you'll also find out that people don't trust Limiteds. One reason is that traditionally people used them for a fresh start after going bankrupt and being barred from operating a domestic company. It also appears as if ltds attract more than their statistically fair share of douchebags, ruining it for everyone else.
Also, and I know people differ on this, but I kinda think paying taxes isn't the worst thing there is (and is probably a moral obligation). There are also possible downsides from avoiding taxes & social sec contributions, like not having the kind of certificate for your income your next landlord might want, the inability to join public health insurance and the risk of managing all your retirement funds yourself – a friend of mine lost the two million € he had saved in his limited when Royal Bank of Scotland(?) went under.
I'd recommend against that. You'll probably be fine as a sole proprietor (Einzelunternehmen).
A separate legal entity (UG / GmbH / Limited / whatever) is mainly useful for three things:
- avoiding personal liability
- shared ownership
- tax optimisation
For a website like this, there is practically no liability to worry about. And if you don't have a partner, you don't need to worry about shared ownership.
For tax purposes, the overhead of a legal entity only pays off if you already have a lot of revenue (in Austria, more than 200k€ per year)
"Limited liability" is mainly related to financial liability (taxes, wages, payments for supplies). If you are worried about your software accidentally deleting all your users files, getting insurance would probably be better than founding a GmbH (and more affordable too).
You can form a US corporation for approximately 100-200 per year in most states (California being a notable much more expensive exception.) There is no requirement that you actually live in the US or even visit.
My junior (at the time) coworker created the 64bit implementations by reading the original papers. But you should be able to find other implementations on github now, since the paper has been out for a while. Our code is pretty tied to software (our allocation / buffer handling).
In hindsight, it might not have been the best idea to say. Hey you just started working with C++ and never worked with SIMD, so yeah... I need to extend this SIMD Fast PFOR scheme to 64bit. But he ended up doing quite well.
Yes, I guessed that it doesn't have a negative connotation for you. That's why I mentioned it, so you could be aware of what the name brings with it in part of the world - perhaps I should have been a bit more verbose about that.
The background is that Hitler used "Hart wie Kruppstahl, zäh wie Leder, flink wie ein Windhund" (Hard as Steel from Krupp, tough as leather, fast as a greyhound) in a bunch of speeches about how to model the german youth. Additionally Krupp Stahl was using forced labour during the war.
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...