> Thanks guys, I have already tried WAL and it does speed things up, but I
> still need the daily processing to be done asynchronously. The computations
> are complex, involving around 16 inputs from the player table and resulting
> in 8 outputs. This is core to the game and not a simple score leaderboard.
> So my options appear to be:
>
> 1. Hope that someone addresses my other thread about async I/O not working
> for me
> 2. Create my own mechanism for asynchronous DB transactions
> 3. Deal with writes that fail due to BUSY - just handle the critical ones,
> drop the others
> 4. Experiment with using a separate DB for the leaderboard results, since a
> separate table won't work
> 5. Switch to NoSQL
> 6. Look at the feasibility of holding results in memory and incrementally
> injecting them into the player table
> 7. Some other ideas?
>
8. Use background thread with read-only access to calculate scores. Forward
result to main thread via some API.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
