6a18a411a3
Currently, pipeline schedule worker is unstable because it's sometimes killed by excessive memory consumption. In order to improve the performance, we add the following fixes: 1. next_run_at is always real_next_run, which means the value always takes into account of worker's cron schedule 1. Remove exlusive lock. This is already covered by real_next_run change. 1. Use RunPipelineScheduleWorker for avoiding memory killer. Memory consumption is spread to the multiple sidekiq worker. |
||
|---|---|---|
| .. | ||
| bridge.rb | ||
| build_trace_chunks.rb | ||
| build_trace_section_names.rb | ||
| builds.rb | ||
| group_variables.rb | ||
| job_artifacts.rb | ||
| pipeline_schedule.rb | ||
| pipeline_schedule_variables.rb | ||
| pipeline_variables.rb | ||
| pipelines.rb | ||
| runner_projects.rb | ||
| runners.rb | ||
| stages.rb | ||
| trigger_requests.rb | ||
| triggers.rb | ||
| variables.rb | ||