Skip to content
代码片段 群组 项目
该项目从 https://gitlab.com/gitlab-org/gitlab.git 镜像。 拉取镜像更新于
  1. 7月 25, 2024
  2. 7月 23, 2024
  3. 7月 22, 2024
  4. 7月 19, 2024
  5. 7月 18, 2024
  6. 7月 16, 2024
  7. 7月 15, 2024
  8. 7月 12, 2024
    • Oscar Tovar's avatar
      Parse affected ranges only once · e6867b43
      Oscar Tovar 创作于
      Previously, the version range matchers used by vulnerability scanning
      always constructed a new affected range when calling the `affected?`
      method. If called sparingly, the performance of the method can be seen
      as acceptable, but if done continuously - in a loop for example - then
      the performance of the matcher begins to suffer. To address this, the
      matcher class now initializes the affected range only once at the
      beginning, and re-uses the same instance for future comparisons. This
      means that we improve the memory footprint significantly when it's
      called in loops as is the case with Continous Vulnerability Scanning
      where we've seen allocations in the realm of GiB. By proxy, this
      improves the performance of the Sidekiq instance that CVS runs on
      because the garbage collector does not need to prune as many unreachable
      objects in memory.
      
      Changelog: performance
      未验证
      e6867b43
  9. 7月 11, 2024
  10. 7月 10, 2024
  11. 7月 09, 2024
  12. 7月 06, 2024
  13. 7月 05, 2024
  14. 7月 04, 2024
  15. 7月 03, 2024
  16. 7月 02, 2024
  17. 6月 29, 2024
  18. 6月 28, 2024
  19. 6月 27, 2024
加载中