Skip to content

Investigate why HB is slow #122

@radmilak

Description

@radmilak

Investigate the infamous "general slowness" in HB.
What we know:

  • It does not happen constantly - seems to go in "waves" that last several hours
  • Effects all tools, though larger ProTo-tools or tools where there is a lot of computation between gui reloads are more effected due to bigger chance for ProTo to timeout (default 30s)
  • Seems at least sometimes to also effect the general HB gui (clicking in the menu, loading a tool before any input is given)
  • There might be a connection to what happens on the server - on one occasion we knew there were big jobs running when HB was very slow, pausing the jobs did not help though
  • All instances are equally effected (dev, sandbox, /hb)
  • One of the theories is that there is race condition/resource blocking happening somewhere, perhaps on the shelves or in genome-related resources, though on one occasion GSuite parsing was timed and identified as taking very long time and we didn't find it access any shared resources
  • Another theory is that this is somehow related to Galaxy/how jobs are started
  • There is nothing exceptional found in logs except ProTo timeouts when slowness occurs
  • Sveinung: It is probable it could be something with the server and not software
  • Sveinung: It could be related to the forking of the process in ProTo

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions