0
0
Fork 0
mirror of https://github.com/go-gitea/gitea synced 2025-01-01 13:04:37 +01:00
gitea/models/fixtures
Lunny Xiao fbe6d9dc6b
Use batch database operations instead of one by one to optimze api pulls (#32680)
Resolve #31492

The response time for the Pull Requests API has improved significantly,
dropping from over `2000ms` to about `350ms` on my local machine. It's
about `6` times faster.

A key area for further optimization lies in batch-fetching data for
`apiPullRequest.ChangedFiles, apiPullRequest.Additions, and
apiPullRequest.Deletions`.

Tests `TestAPIViewPulls` does exist and new tests added.

- This PR also fixes some bugs in `GetDiff` functions.
- This PR also fixes data inconsistent in test data. For a pull request,
the head branch's reference should be equal to the reference in
`pull/xxx/head`.
2024-12-11 05:15:06 +08:00
..
access.yml
access_token.yml
action.yml
action_artifact.yml
action_run.yml
action_run_job.yml
action_runner_token.yml
action_task.yml
attachment.yml
branch.yml
collaboration.yml
comment.yml
commit_status.yml
commit_status_index.yml
deploy_key.yml
email_address.yml
external_login_user.yml
follow.yml
gpg_key.yml
gpg_key_import.yml
hook_task.yml
issue.yml
issue_assignees.yml
issue_index.yml
issue_label.yml
issue_user.yml
issue_watch.yml
label.yml
lfs_meta_object.yml
login_source.yml
milestone.yml
mirror.yml
notice.yml
notification.yml
oauth2_application.yml
oauth2_authorization_code.yml
oauth2_grant.yml
org_user.yml
project.yml
project_board.yml
project_issue.yml
protected_branch.yml
protected_tag.yml
public_key.yml
pull_request.yml
reaction.yml
release.yml
renamed_branch.yml
repo_archiver.yml
repo_indexer_status.yml
repo_license.yml
repo_redirect.yml
repo_topic.yml
repo_transfer.yml
repo_unit.yml
repository.yml
review.yml
star.yml
stopwatch.yml
system_setting.yml
team.yml
team_repo.yml
team_unit.yml
team_user.yml
topic.yml
tracked_time.yml
two_factor.yml
user.yml
user_blocking.yml
user_open_id.yml
user_redirect.yml
watch.yml
webauthn_credential.yml
webhook.yml