Adobe Community: Message List - Why does it take so long when adding a new topic in RH10 with PushOK SVN

Re: Why does it take so long when adding a new topic in RH10 with PushOK SVN

forums_noreply@adobe.com — Fri, 15 Aug 2014 14:59:07 GMT

Rick,

Thanks for the quick response. We do have a working copy on our own machines, with the repository holding the source control version. I agree it sounds as though that is what's happening. Being new users to this system perhaps there's a setting we are missing. I'll do some further testing and report back the results.

Thanks,

Joe

Re: Why does it take so long when adding a new topic in RH10 with PushOK SVN

forums_noreply@adobe.com — Fri, 15 Aug 2014 14:33:46 GMT

Hi there

The behavior you are describing would seem to indicate the project is actually stored on a network drive. Now I know that source control simply HAS to be in a central location, but generally when you configure it for use, you have the main repository on a server somewhere, but you also nominate a "Working Folder" which is usually on your local file system. (C: or D:) So when you check out a topic to work on it, the Working folder maintains the local copy and there should be no lag. When you check it back in, the local copy is then copied back to the main repository.

Perhaps check to ensure you have configured a local location for the Working Folder?

Cheers... Rick

Why does it take so long when adding a new topic in RH10 with PushOK SVN

forums_noreply@adobe.com — Fri, 15 Aug 2014 14:13:21 GMT

RH10 / Window 7 / PushOK SVN

After ugrading from RH8 to RH10, we installed PushOK SVN and the TortoiseSVN Repository browser for our doc team as our source control system, after having used RoboSource Control 3.1 when we had RH8.. Whether in the office or working remotely via VPN, when we add a new topic it can take 1-3 minutes for the topic to actually be ready for input.

Checking in edited topics when closing the project can also take a good deal of time. I expected some of that for those of us using VPN remotely but for those in-house I didn't. Our IT guys are at a loss. They don't believe it's the network.

Is this a common issue? Is there a way around it? Or is there something that comes into play that we are not even considering? OR??

Any help would be greatly appreciated.

Regards,

Joe Pollock