Skip to content

Performance improvement #23

@stigfaerch

Description

@stigfaerch

When setting up crontab as long running, it consumes far to much cpu when idle (no tasks to execute).
The reason is the database is been queried continuously/non-stop in a loop for new tasks.

On my local machine (5%-8%):
Image

On my local machine, Implementing an idle sleep (0% or 0,7% when checking)
Image

Pull request incoming...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions