Are you saving for retirement or buying property? Then start filling your 3rd pillar (Säule 3a) first because of the tax cut. Ideally in a low cost provider (viac/finpension), but the bank you already have probably has an offer too. It might be a bit more expensive than viac, but still much better than not investing. Stay away from 3rd pillar at insurance companies, they might be hard to cancel. Do yourself a favor and do this just for the tax cut.
If you max out the 3a, you can start of thinking investing elsewhere. IBKR is the cheapest to buy a US domiciled world ETF. But the UX is not super easy and you will have to fill all transactions manually in the tax report.
Neon with investments is another option I can recommend if you prefer a swiss company and a simple user interface. Fees are low if you set up a savings plan and pick one of the 0% ETFs
It's difficult to say these numbers are believable or not as they depend on speed and pedal input, but given my own experience and reading some tests/forum, they are off by 2x to 3x.
This could really help in some corporate network scenarios, where batch jobs run behind a proxy. That usually rules out pull based monitoring while this seems easy to setup
I agree, many of the monitoring tools are much more powerful than this, but also a lot harder to set up. The goal was to build something with as little friction as possible that you can set up in under a minute, which makes it viable for any one-off script you might be running.
sorry for not being clear again. by saying this number does not represent full fsync operation, I meant it doesn't include the SSD write time. this is the time to update KVs internal memory structure + adding to write buffers.
this is fair because we provide transactional guarantee and immediate consistency, regardless of the state of the append-only write buffer entry. during that speed, for a given key, the value might change and a new write buffer entry might be added for the said key before the write buffer had the chance to complete (as you mentioned the actual write on disk is slower) but the conflict resolution still ensures the write of the last valid entry and skips the rest. before this operation HPKV is acting like an in-memory KV store.
