1. 18 9月, 2021 1 次提交
    • M
      opt(Restore): Make restore map phase faster (#8038) · 00600944
      Manish R Jain 提交于
      With this change, we can get ~450 MBps output throughput for map phase sustained. This is what we got on a 48 core AWS machine.
      
      ```
      alpha1    | I0917 08:03:27.921912      17 restore_map.go:547] Restore MAP 01h04m30s len(reqCh): 0 len(writeCh): 0 read: 472 GiB. output: 1.6 TiB. rate: 437 MiB/sec. nextFileId: 2474 writers: 0 jemalloc: 0 B.
      alpha1    | I0917 08:03:27.921934      17 restore_map.go:559] Restore MAP Done in 01h04m30s.
      ```
      
      Changes:
      * Make numGo equal to number of cores
      * Don't throttle.
      * Create a bigger buffer before calling merge
      * Rewrite mapper to remove sendForWriting out of the critical path.
      * Fix up a deadlock
      * Fix up the mapper
      * add write ch
      * Use many goroutines to create map files
      * Use fewer goroutines
      * Use 75% of the cores for mapping
      * Stagger the writes
      * Half writers can write at a time
      * Print num writers
      * Range for file would be 1/4 to 1
      * Reduce number of pending requests
      Co-authored-by: NAhsan Barkati <ahsanbarkati@gmail.com>
      00600944
  2. 17 9月, 2021 1 次提交
    • D
      fix(contrib): Quote strings in backup script. (#8035) · f6e8779a
      Daniel Mai 提交于
      Quote the bash strings in the backup script. This is important
      especially for the command-line arguments that can have shell special
      characters like passwords with special characters. For example, passing
      in a password as 'abc!123$456' should not get interpreted with the ! and
      $ characters from bash.
      f6e8779a
  3. 16 9月, 2021 5 次提交
  4. 15 9月, 2021 2 次提交
  5. 14 9月, 2021 1 次提交
  6. 08 9月, 2021 2 次提交
  7. 04 9月, 2021 1 次提交
  8. 03 9月, 2021 2 次提交
  9. 02 9月, 2021 1 次提交
  10. 01 9月, 2021 1 次提交
    • N
      fix(lambda): monitor lambda server, fix performance issue, remove lambda logs... · 05a3958e
      Naman Jain 提交于
      fix(lambda): monitor lambda server, fix performance issue, remove lambda logs from extensions (#8006)
      
      Running lambda script in a new context adds a performance penalty.
      This PR adds a health monitor in alpha that periodically pings lambda servers to check their responsiveness. The unresponsive lambda server ( configurable via --lambda=restart-after flag, default is10s) is restarted.
      Also, this PR removes the lambda logs from the GraphQL response's extension. Instead, they are spit out in alpha logs itself with the prefix [LAMBDA-${ns}]
      05a3958e
  11. 31 8月, 2021 1 次提交
  12. 30 8月, 2021 3 次提交
  13. 27 8月, 2021 1 次提交
  14. 25 8月, 2021 3 次提交
    • N
      [BREAKING] feat: bring dgraph-lambda to dgraph, alpha launches lambda server (#7973) · 12c3ef56
      Naman Jain 提交于
      This PR brings in dgraph-lambda to dgraph repo.
      
      Adds a new super flag --lambda. It has 3 sub flags url (earlier --graphql lambda-url), cnt and port. --lambda url when set, overrides other subflags.
      Alpha launches lambda servers based on the above flags.
      Updates docker file and build script for necessary changes for nodejs.
      Load balance the lambda requests using round-robin policy.
      Note: Users are free to set up their own lambda server and use --lambda url flag. That would need changes in the lambda response.
      12c3ef56
    • A
      opt(codec): return nil instead of a new bitmap (#7997) · 466982d0
      Ahsan Barkati 提交于
      Return `nil` in from FromListWithCopy instead of a new bitmap.
      We should also do the same for FromList.
      466982d0
    • A
      opt(cache): Use Ristretto to store posting lists (#7995) · c051c2f5
      Ahsan Barkati 提交于
      - Use some nifty techniques to make Ristretto caching work with MVCC posting lists.
      - Use posting list cache by default.
      - Set max pending to 64 by default.
      
      This PR significantly improves query performance. This coupled with Roaring Bitmaps has shown to improve query latency by 20x for 50% of user queries, and 100x for 25% of them.
      Co-authored-by: NManish R Jain <manish@dgraph.io>
      c051c2f5
  15. 19 8月, 2021 1 次提交
    • N
      feat(acl): allow access to all the predicates using wildcard (#7991) · 3504044d
      Naman Jain 提交于
      There are usecases that need read/write/modify permissions over all the predicates of the namespace. It is quite tedious to manage the permissions every time a new predicate is created.
      This PR adds a feature to allow a group, access to all the predicates in the namespace using wildcard dgraph.all.
      
      This example provides to dev group, read+write access to all the predicates
      
      mutation {
        updateGroup(
          input: {
            filter: { name: { eq: "dev" } }
            set: { rules: [{ predicate: "dgraph.all", permission: 6 }] }
          }
        ) {
          group {
            name
            rules {
              permission
              predicate
            }
          }
        }
      }
      
      NOTE: The permission to a predicate for a group (say dev) is a union of permissions from dgraph.all and the permissions to specific predicate (say name). So suppose dgraph.all is given READ permission, while predicate name is given WRITE permission. Then the group will have both READ and WRITE permission.
      3504044d
  16. 18 8月, 2021 2 次提交
  17. 17 8月, 2021 2 次提交
  18. 13 8月, 2021 2 次提交
  19. 12 8月, 2021 2 次提交
  20. 10 8月, 2021 3 次提交
  21. 02 8月, 2021 3 次提交