Skip to content
Snippets Groups Projects
Select Git revision
  • ag-test
  • rs-test
  • master default protected
  • test-me-pa
  • mksionek-master-patch-52381
  • new-branch-10
  • test-conflicts
  • test-suggestions
  • alejandro-test
  • patch-25
  • winh-test-image-doscussion
  • stg-lfs-image-test-2
  • stg-lfs-image-test
  • test42016
  • issue_42016
  • issue-32709
  • add-codeowners
  • ClemMakesApps-master-patch-62759
  • bvl-staging-test
  • bvl-merge-base-api
  • v9.2.0-rc6 protected
  • v9.2.0-rc5 protected
  • v9.2.0-rc4 protected
  • v9.2.0-rc3 protected
  • v9.1.4 protected
  • v9.2.0-rc2 protected
  • v9.2.0-rc1 protected
  • v9.1.3 protected
  • v8.17.6 protected
  • v9.0.7 protected
  • v9.1.2 protected
  • v9.1.1 protected
  • v9.2.0.pre protected
  • v9.1.0 protected
  • v9.1.0-rc7 protected
  • v9.1.0-rc6 protected
  • v9.0.6 protected
  • v9.1.0-rc5 protected
  • v9.1.0-rc4 protected
  • v9.1.0-rc3 protected
40 results

models

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Yorick Peterse authored
    Performance is improved in two steps:
    
    1. On PostgreSQL an expression index is used for checking lower(email)
       and lower(username).
    2. The check to determine if we're searching for a username or Email is
       moved to Ruby. Thanks to @haynes for suggesting and writing the
       initial implementation of this.
    
    Moving the check to Ruby makes this method an additional 1.5 times
    faster compared to doing the check in the SQL query.
    
    With performance being improved I've now also tweaked the amount of
    iterations required by the User.by_login benchmark. This method now runs
    between 900 and 1000 iterations per second.
    72f428c7
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    Name Last commit Last update
    ..
    project_spec.rb
    user_spec.rb