Skip to main content
B
bonniem45460749
Inspiring
September 24, 2016
Answered

Rh2015 sloooow saves

  • September 24, 2016
  • 1 reply
  • 569 views
  • When I press Ctrl+S, the save can take up to 20 seconds; if I click the interface during that time, I'll get the NOT RESPONDING notification from Windows 7 Enterprise.
  • The later in the day, the longer the saves. Closing and opening Rh does not shorten the save times and neither does rebooting Windows.
  • Rh is installed on my C: drive and my project is on my own E: drive. I tried moving the project to my C: drive but there was no improvement.
  • There is no difference between saving a one-character change with one topic open or saving more changes with more topics open.
  • We have been using git for version control for many years, but the slow saves have been going on for only a couple of weeks.
  • I do not have a backup program running on my workstation.

I suspect that this has something to do with Windows 7, but Rh2015 is the only app that's been suffering from slow saves. What's Rh2015 doing during saves that is sooooo hard to do quickly? What software package did Microsoft release within the last 30 days that might have caused a problem?

    This topic has been closed for replies.
    Correct answer bonniem45460749

    What I would suggest is what is in Rick's video and regardless of where the

    project is.

    The other thing I once encountered was IT adding a new on the fly backup

    that slowed things up.


    I asked our IT guy if there were anything added recently, such as a desktop management system. He said no, and also that any backup I might have going would be Box synchronization or something that I myself would have to set up.

    As for the video, is WTFV the new RTFM?

    I appreciate how awesome Captivate is. I also know that I absorb written material better than videos.

    "Select File > Options > Clear project cache (.cpd) file before opening any project" was actually the fastest route between A and B in this case.

    Thanks!

    1 reply

    Captiv8r
    Captiv8r
    Legend
    September 24, 2016

    I'm very surprised to hear you say that moving from the E drive to the C drive made no change. Normally I would expect sllllooooooowwwww behavior if a project is on a network drive. Move it to the C drive and ZING! Speeds right up!

    Perhaps you might try what is outlined in the video linked below and see if it improves anything.

    Click here to view

    Cheers... Rick

    B
    bonniem45460749Author
    Inspiring
    September 24, 2016

    The E: drive is local, not network. All my apps are installed on a solid-state C: drive, and I have an enormous local E: drive that spins. That's why my third bullet specified that the E: drive was local.

    So Rh is communicating with its source files over a local bus, not a network connection.

    I am finding that the save times are slow sometimes and fast others within the same hour, and there ain't no rhyme or reason to it.

    Captiv8r
    Captiv8r
    Legend
    September 24, 2016

    Through the years of my participating here in the support forums you would be surprised at how many people use network drives and are utterly convinced that they are local drives because they see the drive letters on their own PC.

    Then again, I've seen many strange things in years of support. When one lady saw the first 3.5 inch floppy, she insisted it was one of those new "hard drives" because of the hard plastic casing. LOL

    When you say the E drive is on a "local bus", do you mean that it's connected to the motherboard or that it's a USB drive?

    Did you try what was outlined in the video? If not, why not?

    Cheers... Rick

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices