Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
d8dd7fa0
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
前往新版Gitcode,体验更适合开发者的 AI 搜索 >>
提交
d8dd7fa0
编写于
2月 21, 2020
作者:
G
GitLab Bot
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Add latest changes from gitlab-org/gitlab@master
上级
4d0c4705
变更
4
隐藏空白更改
内联
并排
Showing
4 changed file
with
24 addition
and
3 deletion
+24
-3
changelogs/unreleased/rs-keep-divergent-refs-column.yml
changelogs/unreleased/rs-keep-divergent-refs-column.yml
+5
-0
db/migrate/20200220180944_add_keep_divergent_refs.rb
db/migrate/20200220180944_add_keep_divergent_refs.rb
+11
-0
db/schema.rb
db/schema.rb
+2
-1
doc/development/sidekiq_style_guide.md
doc/development/sidekiq_style_guide.md
+6
-2
未找到文件。
changelogs/unreleased/rs-keep-divergent-refs-column.yml
0 → 100644
浏览文件 @
d8dd7fa0
---
title
:
Add keep_divergent_refs to remote_mirrors table
merge_request
:
author
:
type
:
other
db/migrate/20200220180944_add_keep_divergent_refs.rb
0 → 100644
浏览文件 @
d8dd7fa0
# frozen_string_literal: true
class
AddKeepDivergentRefs
<
ActiveRecord
::
Migration
[
6.0
]
include
Gitlab
::
Database
::
MigrationHelpers
DOWNTIME
=
false
def
change
add_column
:remote_mirrors
,
:keep_divergent_refs
,
:boolean
end
end
db/schema.rb
浏览文件 @
d8dd7fa0
...
...
@@ -10,7 +10,7 @@
#
# It's strongly recommended that you check this file into your version control system.
ActiveRecord
::
Schema
.
define
(
version:
2020_02_
14_034836
)
do
ActiveRecord
::
Schema
.
define
(
version:
2020_02_
20_180944
)
do
# These are extensions that must be enabled in order to support this database
enable_extension
"pg_trgm"
...
...
@@ -3689,6 +3689,7 @@ ActiveRecord::Schema.define(version: 2020_02_14_034836) do
t
.
boolean
"only_protected_branches"
,
default:
false
,
null:
false
t
.
string
"remote_name"
t
.
boolean
"error_notification_sent"
t
.
boolean
"keep_divergent_refs"
t
.
index
[
"last_successful_update_at"
],
name:
"index_remote_mirrors_on_last_successful_update_at"
t
.
index
[
"project_id"
],
name:
"index_remote_mirrors_on_project_id"
end
...
...
doc/development/sidekiq_style_guide.md
浏览文件 @
d8dd7fa0
...
...
@@ -167,7 +167,7 @@ Most workers tend to spend most of their time blocked, wait on network responses
from other services such as Redis, Postgres and Gitaly. Since Sidekiq is a
multithreaded environment, these jobs can be scheduled with high concurrency.
Some workers, however, spend large amounts of time _on-
cpu
_ running logic in
Some workers, however, spend large amounts of time _on-
CPU
_ running logic in
Ruby. Ruby MRI does not support true multithreading - it relies on the
[
GIL
](
https://thoughtbot.com/blog/untangling-ruby-threads#the-global-interpreter-lock
)
to greatly simplify application development by only allowing one section of Ruby
...
...
@@ -187,13 +187,17 @@ performance.
Likewise, if a worker uses large amounts of memory, we can run these on a
bespoke low concurrency, high memory fleet.
Note that
M
emory-bound workers create heavy GC workloads, with pauses of
Note that
m
emory-bound workers create heavy GC workloads, with pauses of
10-50ms. This will have an impact on the latency requirements for the
worker. For this reason,
`memory`
bound,
`latency_sensitive`
jobs are not
permitted and will fail CI. In general,
`memory`
bound workers are
discouraged, and alternative approaches to processing the work should be
considered.
If a worker needs large amounts of both memory and CPU time, it should be marked as
memory-bound, due to the above restrction on latency-sensitive memory-bound
workers.
## Declaring a Job as CPU-bound
This example shows how to declare a job as being CPU-bound.
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录