4

I've tested many different operating systems on the same machine. Windows 7, 8, 8.1, OS X, Ubuntu, Linux Mint, Android x86, and Remix OS.

All the Unix-like/based operating systems had in common a near zero shutdown time, maybe like 3 seconds.

All the Windows versions took considerably longer to shut down, I am talking about 30 seconds to one minute.

Is there a general reason for this?

closed as off-topic by Jeff Schaller, cuonglm, Jakuje, chaos, user79743 Jan 30 '16 at 18:56

  • This question does not appear to be about Unix or Linux within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    Elaborate on the state in which you've triggered the shutdown? Were you logged in the desktop gui (Gnome/KDE), etc .. ? – gollum Jan 30 '16 at 11:16
  • 2
    Also my personal experience is that Windows (7, 8.x, not much experience with 10) is quite snappy after a clean install and that there is a direct proportional relation between boot up/shutdown times and the number of days that have passed since the initial setup. I've never experienced this increasing slowdown (at least not at this rate) under a Debian Linux. – gollum Jan 30 '16 at 11:36
  • 4
    I'm voting to close this question as off-topic because it's asking about Windows (tm) behavior; try superuser? – Jeff Schaller Jan 30 '16 at 14:41
  • 2
    @Jeff Schaller This answer is not mainly about why Windows shuts down slowly. This Question is about why Unix and Linux shut down quickly, compared to Windows. Calling that off-topic just because another OS is mentioned sounds like quite a stretch. "Windows" is one of the tags on this SE, so I don't see how comparing Unix and Linux to Windows is off-topic. – Revetahw Jan 30 '16 at 14:49
  • 2
    Just my opinion. You may find more Windows expertise at SU. – Jeff Schaller Jan 30 '16 at 15:13
3

Couple of general thoughts I had over this general question :

(1) During Windows shutdown, most services will generate atleast one event on terminating. Sometimes each service may have many events. Eg "NTP Service terminating", "Printer Driver got signal to terminate", "Printer Driver is flushing the queue" "Printer Driver Exitting". These Events are "objects" and are slow to create and destroy, which adds up to shutdown time.
During shutdown on unix, most processes simply print a line on the console or /var/log/messages and exit. Much faster.

(2) During shutdown, Windows GUI will save a lot of state information, most of which is stored as objects.
CLI on unix has almost nothing to save, except for the shell history file. Most state information is in simple text files. Much faster.

(3) Windows may cache many things and these caches have to be flushed to FileSystem on shutdown.
Caches may be handled better on unix, with periodic "fsync" executions, on better FileSystems. Much faster.

(4) Windows may give each process (or service) a lot more time to exit, and hung processes may stay around longer until forcibly terminated.
Unix may give less time to each process (or service) to exit, and most processes may respond quickly. Much faster.

If there is a specific situation, then there may be a specific correct answer, otherwise, we will have to go with vague, inaccurate, simplistic generalizations.

  • 1
    Exactly the kind of answer I was looking for. – Revetahw Jan 31 '16 at 2:47

Not the answer you're looking for? Browse other questions tagged or ask your own question.