You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devlake.apache.org by "narrowizard (via GitHub)" <gi...@apache.org> on 2024/02/21 03:30:18 UTC
[I] [Refactor][blueprint] Optimize Blueprint Update Endpoint Performance for High Volume Tasks [incubator-devlake]
narrowizard opened a new issue, #6983:
URL: https://github.com/apache/incubator-devlake/issues/6983
<!--
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
Currently, as the number of Blueprints (BPs) scheduled to trigger via cron increases, the time taken to update a single BP through the update endpoint also increases. With about a dozen BPs, the update time is reasonable at around 100ms, but with over 1000+ BPs, the update time approaches nearly 1 second. This increase in latency can negatively impact the user experience, particularly in scenarios where frequent BP updates are necessary.
Given that Apache DevLake is designed to handle development data from various sources at scale, it is essential that its core functionalities, such as updating BPs, are optimized for performance regardless of the number of tasks. Currently, the performance degradation suggests that the update mechanism might not be scaling efficiently and could benefit from a refactor.
## Describe the solution you'd like
Not sure.
## Related issues
No
## Additional context
--
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-unsubscribe@devlake.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Refactor][blueprint] Optimize Blueprint Update Endpoint Performance for High Volume Tasks [incubator-devlake]
Posted by "abeizn (via GitHub)" <gi...@apache.org>.
abeizn closed issue #6983: [Refactor][blueprint] Optimize Blueprint Update Endpoint Performance for High Volume Tasks
URL: https://github.com/apache/incubator-devlake/issues/6983
--
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-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Refactor][blueprint] Optimize Blueprint Update Endpoint Performance for High Volume Tasks [incubator-devlake]
Posted by "narrowizard (via GitHub)" <gi...@apache.org>.
narrowizard commented on issue #6983:
URL: https://github.com/apache/incubator-devlake/issues/6983#issuecomment-1955819562
Seems that devlake will regenerate all cronjob when I update a blueprint.
It causes performance issue if there are thousands of bps.
--
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-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org