Mousius opened a new pull request #9128: URL: https://github.com/apache/tvm/pull/9128
I took a look at the time taken by each stage in the Jenkins pipeline and
what comprises the 6 hour CI build time. CPU Integration tests took `60`
minutes of the `100` minutes of `Build: CPU`. By adding `python3: CPU` with
just those Integration tests, it lines up with `python3: GPU` and `python3:
i386` which both take a similar amount of time and takes roughly 60 minutes off
the overall run time.
Numbers copied from sample successful run (final time approx: 358 minutes):
|Phase|ID |Job |Minutes
|Start|
|-----|-----------------------------|------|---------------------------------------------|-----|
|0 |0 |Sanity|3
|0 |
|1 |0 |BUILD: arm|2
|3 |
|1 |1 |BUILD: i386|33
|3 |
|1 |2 |BUILD: CPU|100
|3 |
|1 |3 |BUILD: GPU|25
|3 |
|1 |4 |BUILD: QEMU|6
|3 |
|1 |5 |BUILD: WASM|2
|3 |
|2 |0 |java: GPU|1
|103 |
|2 |1 |python3: GPU|66
|103 |
|2 |2 |python3: arm|22
|103 |
|2 |3 |python3: i386|70
|103 |
|3 |0 |docs: GPU|3
|173 |
|3 |1 |frontend: CPU|40
|173 |
|3 |2 |frontend: GPU|185
|173 |
|3 |3 |topi: GPU|110
|173 |
| | | |
| |
Numbers predicted after change (final time approx: 293 minutes):
|Phase|ID |Job |Minutes
|Start|
|-----|-----------------------------|------|---------------------------------------------|-----|
|0 |0 |Sanity|3
|0 |
|1 |0 |BUILD: arm|2
|3 |
|1 |1 |BUILD: i386|33
|3 |
|1 |2 |BUILD: CPU|35
|3 |
|1 |3 |BUILD: GPU|25
|3 |
|1 |4 |BUILD: QEMU|6
|3 |
|1 |5 |BUILD: WASM|2
|3 |
|2 |0 |java: GPU|1
|38 |
|2 |1 |python3: GPU|66
|38 |
|2 |2 |python3: arm|22
|38 |
|2 |3 |python3: i386|70
|38 |
|2 |4 |python3: CPU|60
|38 |
|3 |0 |docs: GPU|3
|108 |
|3 |1 |frontend: CPU|40
|108 |
|3 |2 |frontend: GPU|185
|108 |
|3 |3 |topi: GPU|110
|108 |
--
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]
