sstojak1 opened a new issue, #7557:
URL: https://github.com/apache/incubator-devlake/issues/7557

   <!--
   Licensed to the Apache Software Foundation (ASF) under one or more
   contributor license agreements.  See the NOTICE file distributed with
   this work for additional information regarding copyright ownership.
   The ASF licenses this file to You under the Apache License, Version 2.0
   (the "License"); you may not use this file except in compliance with
   the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
   
   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
   -->
   
   ## What and why to refactor
   What are you trying to refactor? Why should it be refactored now?
   CalculateChangeLeadTimeMeta subtask is slow when there are a lot of records 
in the tables that are used to calculate the needed metrics that will 
eventually end up in the 'project_pr_metrics' table.
   Queries that are slow for us are the ones that are called in 
`getFirstCommit` and `getFirstReview` methods.
   They are querying `pull_request_commits` and `pull_request_comments` tables. 
   Our fix was to add an index to `pull_request_id` on both tables.
   
   ## Describe the solution you'd like
   How to refactor?
   Introduce index by pull_request_id for `pull_request_commits` and 
`pull_request_comments` tables.
   
   ## Related issues
   Please link any other
   
   ## Additional context
   Add any other context or screenshots about the feature request here.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to