View Single Post
Old 09-30-2017, 10:03 AM   #9
dwig
Wizard
dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.
 
dwig's Avatar
 
Posts: 1,613
Karma: 6718541
Join Date: Dec 2004
Location: Paradise (Key West, FL)
Device: Current:Surface Go & Kindle 3 - Retired: DellV8p, Clie UX50, ...
Quote:
Originally Posted by BetterRed View Post
@yogi62 - couple of ideas...
Makes me wonder if the hard disk is failing
...
BR
My thought as well.

It has now been quiite a while ago, but I had this happen to me back in, I believe, the Calibre 1.x days. Over a period of a month or so, calibre began to take a rather long time to launch. I didn't notice any slow down in other apps, but there were likely some. My HD failed eventually, and when replaced calibre's startup was significantly faster.

Failing HDs return read and write errors. Operating systems simply retry the disk operations multiple times before "throwing in the towel" and notifying the user. When launching an app package like calibre that is comprised of a large number of small files there will be a lot of disk reads and possibly some writes. If the OS is constantly having to retry the disk operations it can add up to a substantial increase in load time.
dwig is offline   Reply With Quote