Bugzilla – Full Text Bug Listing
| Summary: | ci.eclipse.org/xtext terribly slow | ||
|---|---|---|---|
| Product: | Community | Reporter: | Christian Dietrich <christian.dietrich.opensource> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | frederic.gurr, mikael.barbero, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
| Bug Depends on: | 546150 | ||
| Bug Blocks: | |||
|
Description
Christian Dietrich
hipp3 (the mcahine on which your builds are running) is under high load, as everyone is building at the same time (see https://accounts.eclipse.org/committertools/infra-status). The new infra will provide better isolation so you should not see such variations once you'll be migrated. jenkins is unusable for us right now. what has changed? We reduced the number of executors from 4 to 2 to reduce the overall load on hipp3. The load on the host machine is constantly high and Xtext is one of the few projects on hipp3 that run a lot of builds with high CPU usage. Please try to utilize https://jenkins.eclipse.org/xtext/ to spread the load until the xtext JIPP is migrated to our new infra. we need to change all our builds to run on https://jenkins.eclipse.org/xtext/ and this is not done yet unfortunately. ping. right now its not only slow but barely usable at all. can you please have a look if there are some jobs/slaves running amok If you are referring to https://ci.eclipse.org/xtext, then the master seems to be fine. If your builds are taking longer than expected, this is caused by another project on the same physical machine running a lot of (and long) builds. We've reduced the number of builds they can run at the same time, so the load should go down soon. thanks (the dashboard showed we were ddosed by capella Xtext will finish the migration to Jiro soon, therefore I'm closing this issue. |