News for hackers. Stuff that matters.
Re:The SQLite Index Suggester by realPubkey on Tuesday July 05, 2022 @02:36PM (#31992000)
I did something similar for a NoSQL database [1]. The biggest surprise was how much the query performance can change for an index when the data distribution changes slightly. For example using a real distribution for an 'age' field instead of just using a random number like in the test data.

[1] https://rxdb.info/query-optimizer.html

Re:The SQLite Index Suggester by contingencies on Tuesday July 05, 2022 @03:54PM (#31992895)
Sin #5 - Unrepresentative workloads: The common assumption in academic research systems is that the cluster workload is relatively homogenous. Most research evaluations measure performance by running a single job on an otherwise idle cluster. - Schwarzkopf et al, 'The seven deadly sins of cloud computing research' (2014)

.. via https://github.com/globalcitizen/taoup

Re:The SQLite Index Suggester by jessaustin on Tuesday July 05, 2022 @05:27PM (#31993944)
It seems better for birthdate to be stored in the database and age just to be calculated when needed?
Re:The SQLite Index Suggester by realPubkey on Tuesday July 05, 2022 @06:30PM (#31994549)
Yes of course you better store the birthday normally. This was just a projection of the real data set, used in my testings.
Re:The SQLite Index Suggester by HPsquared on Tuesday July 05, 2022 @03:39PM (#31992721)
The 'age' thing might be due to the difference between floats and ints?

Integer "age" has many repeats, but random floats are unique. That, or random ints might be from a large pool, again not many repeats.