I have a Visual SVN Server 3.2 x64 installed in Windows 2008 R2 Server x64.
I have less or more 50 projects with some huge binary files (eg.: 500 MB). After a commit with large change (difference/delta) on those huge binary files i have notice a cpu peak. The server has a bit of traffic (400 clients/hour) and is fully dedicated to Visual SVN Server (AWS EC2 large instance)
After a little investigation i think the problem is in the default compression of the default settings of Visual SVN Server.
Increase cache on delta doesn't help.
Visual SVN Server/subversion has a problem with compression large delta?
Disable it, when the delta between the commits is huge, is a best practice?
Other good suggestion is appreciated. Thanks.
Please, upgrade the server to the most recent version and see whether it helps. I'm pretty sure that the issue you've encountered has been already fixed. If the upgrade won't help, please drop us a line at support#visualsvn.com.
Upgrading from VisualSVN Server 3.2 to the latest 3.5 version should complete in less than 5 minutes. Please read KB95: Upgrading to VisualSVN Server 3.5 guide before beginning the upgrade.
You can get the latest VisualSVN Server installer at the main download page.
VisualSVN Server 3.2.x has reached End of Support in September, 2015. VisualSVN Server 3.2.x is not supported anymore and does not receive security and patch updates.
Please, keep your server instance up-to-date. We timely release maintenance updates for VisualSVN Server with security and bugfixes, and we strongly recommend our users to keep VisualSVN Server at the latest version. The list of fixed vulnerabilities is available for every release in VisualSVN Server changelog and on our release announcements page.
Related
I currently have a dedicated server running the following:
Apache/2.2.32
WHM/CPanel 11.44.3 (build 5)
MySQL Server version: 5.5.40-cll
Because of a security with the version of Cpanel I am told by my hosting company that Cpanel requires an update. The issue they have is because the current Cpanel is version 11.44.3 they can not update to the latest version.
Question, has anyone else had this issue and if so what was if any the resolution.
Many thanks in advance for your time
The hosting company are telling me that the only way around this issue is to have a completely new server configured with all the latest Apache, WHM/CPanel.
This of course would require all the scripts for our web site been transferred to the new server.
You have too old version and to avoid possible issues and downtime, it is recommended to setup and new server with CentOS 7 and latest cPanel and then migrate account one by one. This will allow you to check your websites one by one as you migrate. You should be able to generate full account backup and then you can restore it on a new server.
There is possibility to upgrade the version on your existing server but it is possible that it may cause other issues and you may face lots of issues and downtime.
I have installed certain applications in my VM which has Windows OS Server 2008. Now, If I upgrade the Windows Server to 2012, will it affect my applications in anyway?
I could see that the application is supported in 2012 Server.
It really depends on the applications, but most should be fine. I would recommend taking a snapshot of your old installation so that you can quickly go back to WS 2008 if need be.
Check with application vendor if they support 2012 version OS. Don't upgrade the instance without a snapshot. Most applications should work, unless any App-OS dependency.
I have SQL 2008 R2 on my computer and it works fine with the database. If I install Visual Web Developer 2010 express it says I have to install SQL Express , per it is a dependency. I would prefer to only install web developer.
Will an express installation effect my current installation's operation at all?
Yes they can coexist as they will be installed as separate services - see this forum post
Officially, they can coexist.
Unofficially, my experience with a joint installation is painful. SQL Server patches would fail mysteriously on machines with a joint install. Sometimes you could find fix information in a KB article, sometimes not. Sometimes reinstalling SQL Server worked, sometimes an OS reinstall was required.
You can take the risk on a development server, but I wouldn't do this in production.
I have an instance of Windows Web Server 2008. Do you know if it is possible to upgrade it toward "Windows Standard Server 2008"? (I mean without a complete reinstall and considering that I have the license to do that)
it is possible if your server is x64:
https://serverfault.com/questions/10299/upgrading-windows-server-2008
and for vista is not a complete reinstall, what about Windows Anytime Upgrade?
I'd be very surprised if it did. Even upgrades in Vista between versions is pretty much a complete reinstall.
Currently running Server 2003 but am looking at reinstalling in the near future due to a change of direction with the domains. Should I take this opportunity to install Windows Server 2008 instead?
I would love to play with new technology and the server is only for a small home business so downtime/performance issues aren't really a concern.
I am no expert on Windows server revisions, but the only new feature of Server 2008 I can think of is Hyper-V. But I would try Server 2008 just for Hyper-V, as this VM hypervisor is supposedly much faster than VMware and Virtual PC, and is compatible with Virtual PC virtual disks.
One rule that has served me very well over the years is: Do not upgrade infrastructure components just for the sake of upgrading. If it works well, leave it be. You mentioned that some downtime isn't a big deal, but if the server is actually used then there is a chance it can become a big deal unexpectedly. Why not simply get (or build) a new machine and play with the new operating system there? That way you get the best of both worlds.
There is no Exchange Server 2008. Exchange has always been tightly integrated with IIS which tends to bind it to a specific version of Windows. However, Exchange Server 2007 SP1 can be installed on Windows Server 2008.
Exchange Server 2003, however, cannot run on Windows Server 2008 and I do not believe there are any plans to do so in a future service pack.
Note that Exchange Server 2007 requires x64 architecture, running the 64-bit OS, on a production system. The days of booting /3GB are past - it simply does not provide enough virtual address space for current large databases. Exchange's long-running virtual memory fragmentation problem has not been fixed, it has just been given more virtual address space to work in.