Version control slowness

Did you notice using version control in Designer slows it down? Things like deploy and saving are considerably slower after switching over to Subversion. Are there ways to counter this?

I don't remember this problem from a few years back. Or my memory is not what is used to be.

Tags:

Parents
  • Version Control integration has always negatively impacted performance,
    though how much may depend on the size of your project for all I know.
    Personally I never use it, but I would REALLY like to (as many others have
    said as well) if it integrated with git.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.
  • ab;2490585 wrote:

    ...if it integrated with git.


    We've been asking for git for how many years now?

    ab;2490585 wrote:

    Good luck.


    Apropos.
  • Working in a team it seems quite a must.

    What exactly is slowing it down? Does projects have so many files that keeping it ready for version control takes it's toll? It surely cannot talk to the version control server all the time.
  • On 11/13/2018 12:14 AM, kuronen wrote:
    >
    > Working in a team it seems quite a must.


    I suppose, but I've still seldom (maybe once in a team) used it. The
    difference, in my opinion, is that the Identity Vault acts like a
    repository, and a more-authoritative one since it actually runs the code
    and stores everything as well, like SVN, so everybody always has this
    central store of all current code with which they manage code. SVN is
    just a nice way to do it before pushing changes out via Compare (or in
    fewer cases, Deploy).

    > What exactly is slowing it down? Does projects have so many files that
    > keeping it ready for version control takes it's toll? It surely cannot
    > talk to the version control server all the time.


    I have no access to the code or maybe I'd figure t out, but much more
    likely I would just change the model entirely.

    My dream is to have Designer configured to export eDirectory objects
    (drivers configs, policies, roles, packages, libraries, etc.) to the
    filesystem in a configurable location, and then be able to handle merging
    code into/from there, and then finally to have git integration in that
    location. SVN is okay, but git is fantastic, and I think most of the
    world has made that transition. Considering the offline nature of
    Designer, I think this makes a lot more sense in general, since otherwise
    every commit requires you to be online and able to access the SVN
    repository, and that is painful.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.
Reply
  • On 11/13/2018 12:14 AM, kuronen wrote:
    >
    > Working in a team it seems quite a must.


    I suppose, but I've still seldom (maybe once in a team) used it. The
    difference, in my opinion, is that the Identity Vault acts like a
    repository, and a more-authoritative one since it actually runs the code
    and stores everything as well, like SVN, so everybody always has this
    central store of all current code with which they manage code. SVN is
    just a nice way to do it before pushing changes out via Compare (or in
    fewer cases, Deploy).

    > What exactly is slowing it down? Does projects have so many files that
    > keeping it ready for version control takes it's toll? It surely cannot
    > talk to the version control server all the time.


    I have no access to the code or maybe I'd figure t out, but much more
    likely I would just change the model entirely.

    My dream is to have Designer configured to export eDirectory objects
    (drivers configs, policies, roles, packages, libraries, etc.) to the
    filesystem in a configurable location, and then be able to handle merging
    code into/from there, and then finally to have git integration in that
    location. SVN is okay, but git is fantastic, and I think most of the
    world has made that transition. Considering the offline nature of
    Designer, I think this makes a lot more sense in general, since otherwise
    every commit requires you to be online and able to access the SVN
    repository, and that is painful.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.
Children
No Data