83355336dd
Whenever you push to a branch GitLab will show a button to create a merge request (should one not exist already). The underlying code to display this data was quite inefficient. For example, it involved multiple slow queries just to figure out what the most recent push event was. This commit changes the way this data is retrieved so it's much faster. This is achieved by caching the ID of the last push event on every push, which is then retrieved when loading certain pages. Database queries are only executed if necessary and the cached data is removed automatically once a merge request has been created, or 2 hours after being stored. A trade-off of this approach is that we _only_ track the last event. Previously if you were to push to branch A and B then create a merge request for branch B we'd still show the widget for branch A. As of this commit this is no longer the case, instead we will only show the widget for the branch you pushed to most recently. Once a merge request exists the widget is no longer displayed. Alternative solutions are either too complex and/or too slow, hence the decision was made to settle for this trade-off. Performance Impact ------------------ In the best case scenario (= a user didn't push anything for more than 2 hours) we perform a single Redis GET per page. Should there be cached data we will run a single (and lightweight) SQL query to get the event data from the database. If a merge request already exists we will run an additional DEL to remove the cache key. The difference in response timings can vary a bit per project. On GitLab.com the 99th percentile of time spent in User#recent_push hovers between 100 milliseconds and 1 second, while the mean hovers around 50 milliseconds. With the changes in this MR the expected time spent in User#recent_push is expected to be reduced down to just a few milliseconds. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/35990
108 lines
2.9 KiB
Ruby
108 lines
2.9 KiB
Ruby
# EventCreateService class
|
|
#
|
|
# Used for creating events feed on dashboard after certain user action
|
|
#
|
|
# Ex.
|
|
# EventCreateService.new.new_issue(issue, current_user)
|
|
#
|
|
class EventCreateService
|
|
def open_issue(issue, current_user)
|
|
create_record_event(issue, current_user, Event::CREATED)
|
|
end
|
|
|
|
def close_issue(issue, current_user)
|
|
create_record_event(issue, current_user, Event::CLOSED)
|
|
end
|
|
|
|
def reopen_issue(issue, current_user)
|
|
create_record_event(issue, current_user, Event::REOPENED)
|
|
end
|
|
|
|
def open_mr(merge_request, current_user)
|
|
create_record_event(merge_request, current_user, Event::CREATED)
|
|
end
|
|
|
|
def close_mr(merge_request, current_user)
|
|
create_record_event(merge_request, current_user, Event::CLOSED)
|
|
end
|
|
|
|
def reopen_mr(merge_request, current_user)
|
|
create_record_event(merge_request, current_user, Event::REOPENED)
|
|
end
|
|
|
|
def merge_mr(merge_request, current_user)
|
|
create_record_event(merge_request, current_user, Event::MERGED)
|
|
end
|
|
|
|
def open_milestone(milestone, current_user)
|
|
create_record_event(milestone, current_user, Event::CREATED)
|
|
end
|
|
|
|
def close_milestone(milestone, current_user)
|
|
create_record_event(milestone, current_user, Event::CLOSED)
|
|
end
|
|
|
|
def reopen_milestone(milestone, current_user)
|
|
create_record_event(milestone, current_user, Event::REOPENED)
|
|
end
|
|
|
|
def destroy_milestone(milestone, current_user)
|
|
create_record_event(milestone, current_user, Event::DESTROYED)
|
|
end
|
|
|
|
def leave_note(note, current_user)
|
|
create_record_event(note, current_user, Event::COMMENTED)
|
|
end
|
|
|
|
def join_project(project, current_user)
|
|
create_event(project, current_user, Event::JOINED)
|
|
end
|
|
|
|
def leave_project(project, current_user)
|
|
create_event(project, current_user, Event::LEFT)
|
|
end
|
|
|
|
def expired_leave_project(project, current_user)
|
|
create_event(project, current_user, Event::EXPIRED)
|
|
end
|
|
|
|
def create_project(project, current_user)
|
|
create_event(project, current_user, Event::CREATED)
|
|
end
|
|
|
|
def push(project, current_user, push_data)
|
|
# We're using an explicit transaction here so that any errors that may occur
|
|
# when creating push payload data will result in the event creation being
|
|
# rolled back as well.
|
|
event = Event.transaction do
|
|
new_event = create_event(project, current_user, Event::PUSHED)
|
|
|
|
PushEventPayloadService
|
|
.new(new_event, push_data)
|
|
.execute
|
|
|
|
new_event
|
|
end
|
|
|
|
Users::LastPushEventService.new(current_user)
|
|
.cache_last_push_event(event)
|
|
|
|
Users::ActivityService.new(current_user, 'push').execute
|
|
end
|
|
|
|
private
|
|
|
|
def create_record_event(record, current_user, status)
|
|
create_event(record.project, current_user, status, target_id: record.id, target_type: record.class.name)
|
|
end
|
|
|
|
def create_event(project, current_user, status, attributes = {})
|
|
attributes.reverse_merge!(
|
|
project: project,
|
|
action: status,
|
|
author_id: current_user.id
|
|
)
|
|
|
|
Event.create(attributes)
|
|
end
|
|
end
|