Repository Connection Performance

[tpearsall]

Run CE 4.3.0 on Windoze with a repository on SQL Server 2008.

Opening and saving transformations local on the PDI server are very fast, however, remotely over a VPN connection takes 30+ seconds per transformation. It is a cable connection and is generally quick for other uses. In past cases when I've had a DI Server the saving performed reasonably well so I'm guessing the issue is latency as PDI makes a lot of DB transactions when opening/saving the transformations.

My plan B was to go with a File Based repository, but I haven't seen a work around for PDI-4958.

My questions:
1) Are there settings like connection pooling I should use to improve performance with the repository? Recommendations?
2) Is there a way to address the Slave Server Exists error in setting up a file based repo?
3) Are others not seeing slow repo performance?

Any feedback would be appreciated.

Thanks,
Todd

[EricIsDreaming]

I'm having the same performance issues with a mysql repository over a vpn.

I also tried using a file based repo, and hit the same bug you linked too.

I'm at a loss as to what to try next.

[MattCasters]

If you're on 4.3.0, I'm afraid there's nothing you can do about it as it's already heavily optimized for the DB repository.
Perhaps it would have been better to use a version control system with a local file repository.

[EricIsDreaming]

Thanks for the idea. Unfortunately I started with the local file repository, and hit PDI-4959 :-(

[MattCasters]

Mind you, it doesn't really count as a local repository if you're putting the data on a slow network folder.
Another think I can't understand at all was one person that created a file repository on all possible branches and tags of a subversion tree.
With hundreds of tags and branches and a hundred transformations and jobs all of a sudden you're looking at tens of thousands of entries.

I don't mind anyone doing these things as long as they don't come complaining about "bad performance" :-)