narrowizard opened a new issue, #8142:
URL: https://github.com/apache/incubator-devlake/issues/8142
<!--
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
As a software engineer, I am using devlake to collect developer data since
long time ago. Recently we find that the `_devlake_subtasks` table occurs a
data inflation. It used 750MB after a week from we upgrading devlake v1.0, but
there were only 1000 records in the table.
## Describe the solution you'd like
Solutions from @klesh
1. Reduce the update rate to _devlake_subtasks table when collect data.
2. Store progress info in memory firstly and write it to db in a fixed rate.
## Related issues
No
## Additional context
The issue was
[introduced](https://github.com/apache/incubator-devlake/commit/cb4c0d70f324ddb7302f7a469509c785fb178854#diff-64e114e0c6462173c17c75a58110c37b68efa0e474de118878fb25ce7ea3041bR356-R359)
in v1.0.
--
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: dev-unsubscr...@devlake.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
