infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bowen Li (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-18533) Travis-CI capacity degradation
Date Tue, 02 Jul 2019 18:00:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-18533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877192#comment-16877192
] 

Bowen Li edited comment on INFRA-18533 at 7/2/19 5:59 PM:
----------------------------------------------------------

Hi [~gstein], thanks for sharing the insights. However, the total build time is a totally
different thing than guaranteed build capacity.

As mentioned above, since I started to pay attention to Flink's build queue a few tens of
days ago, I'm in Seattle and I saw no build was kicking off in PST daytime in weekdays for
Flink. Our teammates in China and Europe have also reported similar observations. So we need
evaluate how the large total build time came from - if 1) your number and 2) our observations
from three locations that cover pretty much a full day, are all true, I **guess** one reason
can be that - highly likely the extra build time came from weekends when other Apache projects
may be idle and Flink just drains hard its congested queue.

Please be aware of that we're not complaining about the lack of resources in general, I'm
complaining about the lack of **stable, dedicated** resources. An example for the latter one
is, currently even if no build is in Flink's queue and I submit a request to be the queue
head in PST morning, my build won't even start in 6-8+h. That is an absurd amount of waiting
time.

That's saying, if ASF INFRA decide to adopt a quota system and grant Flink five DEDICATED
servers that runs all the time only for Flink, that'll be PERFECT and can totally solve our
problem now. 


was (Author: phoenixjiangnan):
Hi [~gstein], thanks for sharing the insights. However, the total build time is a totally
different thing than guaranteed build capacity.

As mentioned above, since I started to pay attention to Flink's build queue a few tens of
days ago, I'm in Seattle and I saw no build was kicking off in PST daytime in weekdays for
Flink. Our teammates in China and Europe have also reported similar observations. So we need
evaluate how the large total build time came from - if 1) your number and 2) our observations
from three locations that cover pretty much a full day, are all true, I **guess** one reason
can be that - highly likely the extra build time came from weekends when other Apache projects
may be idle and Flink just drains hard its congested queue.

Please be aware of that we're not complaining about the lack of resources in general, I'm
complaining about the lack of **stable, dedicated** resources. An example for the latter one
is, currently even if no build is in Flink's queue and I submit a request to be the queue
head, my build won't finish in 15h+. That is an absurd amount of waiting time.

That's saying, if ASF INFRA decide to adopt a quota system and grant Flink five DEDICATED
servers that runs all the time only for Flink, that'll be PERFECT and can totally solve our
problem now. 

> Travis-CI capacity degradation
> ------------------------------
>
>                 Key: INFRA-18533
>                 URL: https://issues.apache.org/jira/browse/INFRA-18533
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: CI
>            Reporter: Antoine Pitrou
>            Assignee: Greg Stein
>            Priority: Major
>
> We're witnessing frequent Travis-CI build waits on Arrow that we were not witnessing
before. It seems Travis-CI may have shrunk the capacity that's available to us, or perhaps
Apache projects are making more intensive use of the capacity.
> Either way, it seems it is starting to affect our capacity to iterate quickly on portability
issues and other build failures. [~wesmckinn]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message