-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Matthew Tippett wrote: > Any takers?
It isn't clear what you want. It mostly appears to be people to fix the Phoronix test suite. That is really their problem! SQLite already includes various speed tests. For other people the only benchmark that is relevant is their own. Some think 10MB is a large database while others are in the tens of gigabytes. Some strings are short (eg names), some are longer (eg full pathnames and others very long (eg genetic sequences). Some use SQLite to store 3D data while others are plain old tables that even Excel could handle. Some transactions are small, others are large as percentages of the tables. Quite simply there is no way someone else's benchmark is going to be representative of what you do. If Phoronix wants to be relevant then they need to decide what it is they are benchmarking. You can make SQLite use lots of CPU by doing sorts on large data sets. You can make it do lots of I/O by making a query access far more data than fits in the SQLite cache and the operating system cache (the latter is largely a function of spare RAM). You can make up synthetic scenarios such as "pet shop", "gene splicer", "web log analyzer" etc and code up to them. A critique of those is easy providing the SQL executed and a .dump of the database are provided so they can be reproduced by the shell. Roge -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrIB+oACgkQmOOfHg372QTrbgCfTDFr7109qXh0U7RIqtWapBzw 2bgAn1K5PwA9NKOLSLHa1UUx9cr80Y6z =f+ot -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
