# Cardano-node start time

**URL:** <https://forum.cardano.org/t/cardano-node-start-time/40120>\
**Category:** Operate a Stake Pool\
**Created:** [10 September 2020 13:36 UTC](https://forum.cardano.org/t/cardano-node-start-time/40120 "2020-09-10T13:36:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![COSDpool](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.cardano.org/cosdpool/32/21482_2.png) [@COSDpool](https://forum.cardano.org/u/COSDpool)\
**Post date:** [10 September 2020 14:24 UTC](https://forum.cardano.org/t/cardano-node-start-time/40120/2 "2020-09-10T14:24:14Z")

</div>

Definitely faster startup times for newer node versions are reported when killing with signal `SIGINT` (`killall` sends `SIGTERM` by default):

> [@Restart producer node - 18 minutes to sync](https://forum.cardano.org/t/restart-producer-node-18-minutes-to-sync/39993/4):
>
> thanks @lauris that’s good to know. In version 1.18.0 this was not the case… SIGINT had the same effect as SIGHUP, SIGKILL etc… crash and burn no matter what, with ledger having to catch up from the last checkpoint. We reported this here & sounds like it’s been fixed: Or maybe we’ve seen the huge improvement ourselves in restart speed since our systemd script was set to use SIGINT from the beginning, even though version 1.18.0 didn’t catch that signal at the time (@stiiiif you could also tr…

So you can do this instead:  
`killall -s SIGINT cardano-node`

It might help also to look at some of the other performance considerations linked from that thread. Maybe a coincidence, but 90 seconds is also the timeout for restarting a daemon if it’s running from `systemd` (if not true for you yet, then something you’ll be interested in).

---

_[View the full topic](https://forum.cardano.org/t/cardano-node-start-time/40120)._
