Open amj opened 5 years ago
This requires an index on filename which increases database size ~30% which will be >10gb so I'm going to not implement at this time.
If there are more use cases (than joseki explorer) I'm happy to reconsider.
start = 52.1 gb
sqlite> delete from games where model_id not between 16000000 and 16999999;
vacuum => 6.2 gb
sqlite> delete from eval_games where model_id_1 not between 16000000 and 16999999;
vacuum => 5.5 gb
eval_models, model_stats
vacuum => 5.4 gb
CREATE INDEX game_name ON games (filename);
=> 6.8 gb
e.g.
https://cloudygo.com/v16-19x19/joseki/full/1548398561-tpu-player-deployment-d74dbc759-27cfr-7.sgf