simd

Though we include Boost JSON as a dependency for benchmarking purposes, we do not include it as part of our benchmarks currently.

Describe the bug

Currently keys written to server.conf go undetected.

This means that not only typos go undetected, but lack of validation is a risk during version migration as settings that used to apply in a previous version have no effect in a newer one without warning -- even if new settings are supposed to be used.

To reproduce

• Create a key with a typo.
• Watch the QuestDB

Our users are often confused by the output from programs such as zip2john sometimes being very large (multi-gigabyte). Maybe we should identify and enhance these programs to output a message to stderr to explain to users that it's normal for the output to be very large - maybe always or maybe only when the output size is above a threshold (e.g., 1 million bytes?)

I am finding a product which can replace Elasticsearch.

Doing performance fine tuning, it may be beneficial to have separate code paths if the mask is "all on". Right now there are multiple ways of expressing this paradigm, which are not guaranteed to be optimal on all platforms. Possible ways of checking this are:

1. __all(__mask). Seem to produces good code on all platforms, but uses builtins (that are not recommended for the use outside of stan

Hi,

thank you very much for this cool library.

I noticed that simde_mm512_load_ps is missing while simde_mm512_loadu_ps is implemented. However, both seem to exist for Intel intrinsics (see screenshot). Maybe I oversaw one or maybe they do the same anyways?

Thanks
Lukas

![Screenshot from 2021-10-25 13-28-29](https://user-images.githubusercontent.com/14993470/138687358-aa6b531e-bdc