We're running Artifactory 2.1.3, serving 17000+ artifacts. We've recently run into some performance issues due our current configuration (repo/mysql) and the size of the artifacts being written (some > 100MB). It seems that the suggested configuration for an enviroment like ours is to use repo/filesystem-mysql.
The posts that I've seen on this topic suggest replacing the repo/mysql/repo.xml configuration with repo/filesystem-mysql/repo.xml. I'm sure that would work fine when setting up a new repository. But, is it possible to change from the repo/mysql configuration to repo/filesystem-mysql without losing access to the 17000+ artifacts that have previously been deployed? If so, what is the process I should follow to change from repo/mysql to repo/filesystem-mysql? Thanks for your help, Craig. -- View this message in context: http://forums.jfrog.org/Reconfiguring-Artifactory-Changing-from-repo-mysql-to-repo-filesystem-mysql-tp5577488p5577488.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
