Apache SVN server requirements? [closed] - linux

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
Are there any minimum server requirements for using Apache SVN? If not, what are some general server specifications used for Apache SVN? Any information on server capacities for Apache SVN would be appreciated!

As long as your team is not extremely large, a very decent server is enough. Even a virtual server with about 1 virtual CPU and 1GB RAM running on a decent real CPU is enough. I'd say it doesn't need to be any faster than a server you'd use as a file server.
I'm using it myself on a very limited v-server and it works very well.

I have yet to find an Apache httpd configured Subversion server that's underpowered. Subversion itself doesn't take up a lot of bandwidth. I would still suggest that the server be dedicated. It isn't that Subversion sucks up a lot of power. More likely, whatever else you do will suck up too much power, and it will slow down Subversion. I was at one site that kept on piling more stuff onto the Subversion server (including database services) and then ware upset that Subversion was slow. Everything on that machine was slow.
The main concern would be bandwidth which seems to matter much more than the server itself. Also, be careful with NFS mounted disks (although Netapps seem fine).

I found this http://subversion.apache.org/faq.html#server-requirements but it's probably not enough detail.

Related

Can I make a DIY Cloud server for windows? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
My old parents have been hacked/virus-ed for the nth time.
I have an old HP server.
I thought of rebuilding it with VMWare (free version) or Oracle virtualbox and having them use windows in a controlled environment. I would back it up and patch it, etc. Maybe they RDC to my server.
I assume I would need a Windows server license to allow multiple connections. (I could also use it for myself to host Plex media server.)
At a 10,000 foot level, is this possible or just a technology quagmire?
Super User SE might be a better place for this.
Anyway: Are they using it for anything windows-specific? My parents used to use my Linux-based computer for web browsing, now they use an Android tablet for the same. Running a virtualised Windows on top of the former could've been an alternative. Also, backing up and rolling back is easier if you use virtualisation, just use something else for permanent data storage. Maybe a remote storage with backup and rollback (for ransomware) either your own infrastucture or in the cloud. (like syncthing, owncloud, etc.)
I'm assuming here they don't have trade secrets or plans of a home-built nuclear plant or anything that kind.

Apache couchdb system minimum requirements [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I checked all the documentation of couch DB. There is no mention of the system requirements.
I want to install CouchDB on AWS nano machine and wondering if it is possible.
Question
What are the CoupchDB minimum system requirements? (RAM, CPU, disk)
I have not seen any official minimum requirements. I have the smallest DigitalOcean droplet running Ubuntu Server with the CouchDB 2.1.1 on it (and it previously ran version 1.6.1). It works well, but is only used as a test machine for a development project. The spec is one CPU, 512mb RAM and 20gb SSD disk.
We run CouchDB in production on AWS using Docker. In general, we have found that we need at least a t2.medium for each node to keep up with the CPU and memory demands, i.e. each t2.medium instance has 2 CPU cores and 4GB memory.
We are planning on releasing a more in-depth analysis shortly.

/boot/.IpTables use high cpu in my server [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
i am newbie in network administrator..
One week ago, my server work perfectly. My Server can serves 600++ users at the same time and only use 40% cpu.
Today there is something wrong with my server. My server shows 100% cpu usage when it serves 100 users at the same time.
After i check, i found a process /boot/.IpTables that use high cpu.
What happen with my server? Is my server hacked or what?
This is SS my server process :
OK, looks like your system has been had. I did some googling for /boot/.Iptables, and it appears to be malware.
https://askubuntu.com/questions/407457/help-my-server-has-been-hacked-iptables-and-iptablex-in-boot
https://www.centos.org/forums/viewtopic.php?f=17&t=46704
My personal recommendation would be to take the machine of the network immediately, clone the drive to a USB disk, and re-install (preferably w/ a new set of passwords, and all available patches applied).

Is there a performance difference between running elasticsearch on Linux or Windows? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
elasticsearch can be started as a Windows or Linux service. Is there is any better performance in running it in one environment versus the other in production?
The advantage of using linux for running elasticsearch is that the vast majority of elasticsearch users use this and most of the optimization efforts are linux focused. There's a lot of knowledge out there on how to tune and optimize elasticsearch on linux.
A lot of that probably ports over to windows but it is fundamentally very different in how it behaves with a different kernel, filesystem, networking, etc. I expect things probably work fine in windows but fundamentally you are pretty much on your own tuning it and diagnosing any issues you encounter.
The only reason I could see for attempting to run Elasticsearch in windows at all are 1) you have windows servers available and want to utilize them and it is not negotiable to format their drives with something more sane like Ubuntu or centos 2) it's a small non, mission critical setup where you don't actually care about tuning things or getting meaningful support for any issues you encounter and you happen to have some windows machines available for running elasticsearch.
So, unless you really want to use windows, you probably shouldn't.
The answer to this question is going to be a big fat "it depends." I have to respond to whole-heartedly disagree with the other answer. I have Elasticsearch deployed to production on Amazon Web Services as a Windows service for an enterprise-level application and have never had any problem tuning it or finding help in that regard. The other answer has a point to the extent that the official Elasticsearch documentation apparently assumes you're going to be using Linux, but that's their problem. It does not mean you're going to be on your own.
I suppose that it would be possible to get some comparable hardware and run benchmarks if you really want to find out which one you can make faster, but who has time for that? I doubt that such an experiment would make a difference to anyone but the largest websites on the Internet anyway.
That said, Elasticsearch is built for clustering. You scale by throwing more hardware at it. Linux is necessarily going to be cheaper if for no other reason than that you won't have to pay licensing costs. Unless you already have the hardware or virtual machines, you are most likely going to get more bang for your buck with Linux.

Alternatives to "reboot" after changing crucial files in a working server? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 9 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
Assume I have a server already functioning and providing an app to users. At one moment, I have to modify some crucial /etc/ configuration files. For example, /etc/security/limits.conf.
After I do the changes, documentation usually suggests rebooting the machine.
reboot
But this would imply that all processes in the server die, am I right? So, basically what will happen to the guys checking my app hosted on the server that I just "rebooted"? I think the service will stop for a while. Is there any other command or alternative less painful to do after changing crucial files?
I'm on CentOS & Nginx.
PD: If somebody could provide also a link to the difference between "shutdown" and "reboot" (because I found only some vague things), that would be great.
Easy part first - if you run shutdown your computer ends up being off. As in no power. As in, very difficult to fix remotely :). Reboot restarts everything.
It is fairly rare to require a reboot under linux - the only reason to reboot that I can think of is if you upgraded the kernel, if your machine is crashing really badly, or if you want to install some types of new hardware (RAM, plug-in cards etc).
Mostly, when you edit "important files in /etc", you can restart just a part of the system. For example, you might need to restart just your webserver.
There is no complete rule. Try googling "reload ". For example, googling "reload /etc/security/limits" suggests logging out, then logging back in.

Resources