# Sidekiq s'arrête et ne redémarre pas

**URL:** <https://meta.discourse.org/t/sidekiq-dying-and-not-coming-back-up/111267>\
**Category:** Self-hosting\
**Created:** [Mars 11, 2019, 12:51 UTC](https://meta.discourse.org/t/sidekiq-dying-and-not-coming-back-up/111267 "2019-03-11T12:51:29Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [Mars 11, 2019, 8:15 UTC](https://meta.discourse.org/t/sidekiq-dying-and-not-coming-back-up/111267/5 "2019-03-11T20:15:15Z")

</div>

> [@LeoMcA](#):
>
> what performance impact are we looking at logging every second? I suppose all we’d hang is the sidekiq thread, which is hardly a problem when it’s not working properly anyway.

In my testing it hasn’t caused any noticeable impact. In theory it could cause a very slight performance hit on the Sidekiq process. The impact should be fairly minimal because the logging disk i/o is performed in a separate thread, allowing other things to continue in the main worker thread.

> [@LeoMcA](#):
>
> separate files for the finished and pending jobs

Each JSON object is on its own line, so you can simply do something like

```plaintext
cat sidekiq.log | grep pending

```

And then parse the JSON that you get out of that.

---

_[View the full topic](https://meta.discourse.org/t/sidekiq-dying-and-not-coming-back-up/111267)._