Chris Hill-Scott 505de52d38 Check if any jobs exist before querying jobs ...

At the moment the dashboard does two API calls to find out if a service
has:

1. Scheduled jobs
2. Normal jobs

API calls are slow because they are synchronous, go over the network and
touch the database. We can’t cache these API calls because:
- a scheduled job could become a normal job at any time
- the statistics on a normal job are constantly updating

However there are plenty of services which don’t have any jobs, and
probably never will. And finding out if a service has any jobs is
reliably cacheable (because as soon as a service creates its first job
it has some jobs).

So this commit:
- refactors the way we get scheduled/normal jobs into the job_api_client
  to make the view a bit slimmer
- makes an additional, Redis-wrapped call to find out if any jobs exist
  before trying to get the jobs

This should result in a speedup on the dashboard, and can be used in the
future if there’s anywhere else we want to show or hide something
depending on whether a service has created any jobs (I have some ideas).

2018-07-30 11:14:01 +01:00

..

app

Check if any jobs exist before querying jobs

2018-07-30 11:14:01 +01:00

non_spreadsheet_files

…

spreadsheet_files

…

__init__.py

…

conftest.py

Ensure one-off jobs do not appear on message log page

2018-07-18 08:11:42 +01:00