Skip to content
Snippets Groups Projects
Select Git revision
  • renovate/major-opa
  • spike/go-tools-124-gql
  • spike/go-tools-124
  • main default protected
  • chore/deepmap
  • docs/mas
  • build/notify
  • fix/du
  • defect/diff
  • defect/json
  • chore/schema
  • feat/diff-json
  • chore/typo
  • build/binaries
  • build/changelog-
  • defect/otel
  • chore/otel
  • chore/dep
  • docs/changelog
  • defect/changelog
  • v0.115.3 protected
  • v0.115.2 protected
  • v0.115.1 protected
  • v0.115.0 protected
  • v0.114.0 protected
  • v0.113.5 protected
  • v0.113.4 protected
  • v0.113.3 protected
  • v0.113.2 protected
  • v0.113.1 protected
  • v0.113.0 protected
  • v0.112.0 protected
  • v0.111.1 protected
  • v0.111.0 protected
  • v0.110.2 protected
  • v0.110.1 protected
  • v0.110.0 protected
  • v0.109.0 protected
  • v0.108.0 protected
  • v0.107.0 protected
40 results

dependabot

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Jamie Tanna authored
    The performance of DMD hasn't been particularly great - hence why
    there's been the need to introduce a progress bar for most of the
    operations - and it turns out it's to do with SQLite's transactions[0].
    
    As we're not wrapping any of our updates in a transaction, SQLite is
    producing one for us, which is slower than us managing it ourselves, as
    we know how many `INSERT`s we'll be doing at a given time.
    
    This speeds up considerably, for instance the `integration_test` phase
    currently takes ~90 seconds instead of ~240 seconds, and results in no
    longer even seeing the progress bar on `import`s.
    
    Closes #89.
    
    [0]: https://stackoverflow.com/questions/3852068/sqlite-insert-very-slow
    def9666e
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.