Bug 1500974
| Summary: | Beaker UI cpu intensive | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Michael Petlan <mpetlan> |
| Component: | web UI | Assignee: | beaker-dev-list |
| Status: | CLOSED DUPLICATE | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | achatter, dcallagh, mjia, rjoost |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-06 02:45:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Michael Petlan
2017-10-11 21:27:26 UTC
Could you give an example of a job ID where this happens? Does it happen 100% on that job, or does it occur randomly/with some other pattern? Does this problem happen while the job is still running -- and then go away once the job is finished? In which case, it's likely caused by the 20 second polling loop for job changes. Or does it happen even when the job is already finished? We know that there are some problems with large jobs (in the many thousands of results) which we can improve. If you are seeing the problem on a relatively small job though, then there might be something else going wrong which we aren't aware of. Moving this bug to the Beaker product, as there is nothing to be done here at the packaging level in Fedora. (In reply to Dan Callaghan from comment #1) > Could you give an example of a job ID where this happens? > Going through my jobs, cannot reproduce it right now. Happens quite randomly. > Does it happen 100% on that job, or does it occur randomly/with some other > pattern? Rather randomly, but so far jobs page. > > Does this problem happen while the job is still running -- and then go away > once the job is finished? In which case, it's likely caused by the 20 second > polling loop for job changes. Or does it happen even when the job is already > finished? Not encountered on a non-running job so far. > > We know that there are some problems with large jobs (in the many thousands > of results) which we can improve. If you are seeing the problem on a > relatively small job though, then there might be something else going wrong > which we aren't aware of. What exactly does a 'large job' mean? A job having a high number of recipesets or a job having any number of recipesets, but its recipesets containing too many recipes/tasks inside? What should I do when seeing it again? I.e. firebug, etc. Can I grab more info for you somehow? Well we know that the CPU usage of each iteration of the polling loop must be (roughly) proportional to the size of the job -- but we don't know how big the job has to be to become a problem. It is "size" in any dimension -- ultimately the page is fetching a JSON representation of the complete job (down to the level of results+logs for very task in the entire job) so the larger that JSON blob is, the more CPU time will be spent every 20 seconds on the page. It would help the most if you could just write down job IDs where you see this problem really badly -- bad enough that it hangs your browser or interferes with your ability to use the page. That will help us to figure out exactly how big is "too big" so we can focus our optimisation efforts to make the page more usable. I think this might actually be a dupe of bug 1500142 (effectively). Especially if the problem only appeared in Beaker 24.4. We have discovered quite a lot of places in the UI where it is now re-rendering the HTML once per second, due to a change we made in how the page tracks the recipe watchdog countdown. *** This bug has been marked as a duplicate of bug 1500142 *** |