On 20 Sep 2015, at 11:18pm, James K. Lowden <jklowden at schemamania.org> wrote:
> Rob Willett <mail.robertwillett.com at postfix.robertwillett.com> wrote: > >> Thanks. We?ve got 100 requests a second which may be enough. We?ll >> keep looking though for any time. > > I suppose you know that 100/sec is about 0.1% of what the machine is > capable of. SQLite is really a trivial part of this. Doing things in the obvious way OP is triggering SQLite commands from a web-based interface, with a new process created for each command. Then the new process needs a SQLite database connection and only then can you get down to issuing a SQLite command. OP could redesign his app to call a persistent SQLite server which runs constantly in the background, holding a connection to the SQLite database open. Requires more memory and more programming but it should speed up things quite a bit. Simon.
