Which Would Be Faster? Ram = 128 With DirectAdmin Or 256 With Cpanel
Jul 4, 2007
I have heard that Direct Admin is much faster then cpanel & require much less resources then cpanel... I was just wondering if I get vps with 128 ram with Direct admin on it, would it be better than vps with 256 ram with cpanel installed... I am running 3 websites with almost 10 to 20 users at a time (at max 50).... I like both cpanel & directadmin but was thinking if 128 ram with DirectAdmin can give more speed on 128 then I won't spend more money on 256 with cpanel... If anybody have an opinion then please put it here...
On average, how much memory does cpanel use when compared to a standard directadmin setup?
I've never had a chance to use directadmin before, but I've been reading quite a bit about it around the web and that it uses much less memory than cpanel.
Anyone used both? Which is better for VPS hosting?
I have a direct admin server and I am planning to take backup of all the accounts in my DA server to my friend server. This is just for safety precautions.
I have a reseller account that is hosted at ns1 / ns2.mydomain.com and it is configured via cPanel / WHM and is accessed by mydomain.com
I recently purchased a dedicated server and would like the dedicated server to have a ns3 / ns4.mydomain.com I also would like that the dedicated server be accessed by another domain (other than mydomain.com). Is this possible?
If that is not possible, what way is a good way of doing this?
Has anyone done this or currently running this setup? to try it with my directadmin server first but havent found very good documentation or howtos. Ive looked the last week or so and havent really found anything helpful. So if anyone is running such a setup Id like to know how you did it and how much better if any it is.
I'm new to using directadmin and I've got a problem; I've not yet switched the DNS over to the directadmin server 'cause I want to make sure the sites work first, however I can't find how to view the sites. With cpanel you can go to http://192.168.1.1/~username (where 192.168.1.1 = IP of server and username is username of account). is this possible with directadmin? I can't find anything about it, anywhere.
My understanding is that if I join a webhosting company that operates the cPanel web control panel then my Outlook Express email program would get configured automatically.
However if the webhosting company were to be using DirectAdmin web control panel would I get the same benefit in this respect please?
I've read that php 4 is faster than 5, is this true? I'm not sure which one I should use to host my invision powerboard. It's the only php/mysql site on the server.
I know the assumption is that VPS is faster than shared, but my site currently runs on a shared server with a host that does not oversell, and it runs very fast for a WordPress and gallery site.
I'm certain the shared server is at least a dual CPU monster, and it rarely goes above 5% usage. So if I move this site to a VPS it seems logical to me that it might not be as fast.
I just changed hosts, thinking it would be faster. My homepage uses 53MB of RAM. My old host lets me use ini_set to change this (currently have it at 128MB), my new host doesn't (48MB).
So, I've cut some of the functionality of the site to make it work on the new host. Should I upgrade the hosting plan to higher RAM? Given that the site already works reasonably well on the new host, what type of performance boosts could I expect to see by doubling the RAM?
I am going to upgrade my servers and move all the accounts. Of course DNS IP's will change.
Last time I did this, I just created exactly same DNS on new server (eg. ns11.server.com and ns12.server.com) and updated the IP address of the DNS on the registrar. However it took more than 2 days for some domains to update the new DNS IP address. It was a nightmare.
So my options are: 1) Do the samething as before 2) Create new DNS addresses (eg. ns5.server.com and ns6.server.com) and update the DNS info of all the domains.
I live in Hawaii and half my sites serve Hawaii. Webhosts in Hawaii are really expensive. Does it matter where on the mainland US that I host my sites? Would they serve the fastest if I host them in California considering it's the closest to Hawaii?
These new "rules" make BFD ban faster, checks every minute. BFD only checked every 10 minutes and could miss attackers that show up at the right time. Now we keep 10 minutes of IPs, and ban using that list.
I feel that APF and BFD are still the best choices for protecting my server. Cpanel's new "cphulk" feature has a lot more to go to be as good, plus you have total control with BFD where you can add and change rules to suit your needs as they grow, or modify them for particular problems.
The changes I made are based on the latest version of BFD V0.9, you should have that version installed and WORKING ALREADY.
Remember, they are simply shell scripts that define the log file to keep track of and what keywords to trigger on. You can view them with any text reader.
WARNING: These work for me, USE AT YOUR OWN RISK, always make sure you add your current IP in /usr/local/bfd/ignore.hosts (and) /etc/apf/allow_hosts.rules so you don't accidentally ban yourself!
Inside the below tar.gz file are my modified "rules" files for exim, pure-ftpd, rh_imap, rh_pop3, sendmail and sshd. No changes to the BFD V0.9 main program are needed.
You should change the cron job to run BFD every minute, edit this file: /etc/cron.d/bfd
Change the line in that file to this so it runs every minute: */1 * * * * root /usr/local/sbin/bfd -q
I checked the CPU load and since it's reading only a small part of the log file every minute, the CPU load isn't bad, it's done in about 8 seconds on my system. Expect a small rise in load average since it is doing work more often.
The "rules" files are contained in your server directory: /usr/local/bfd/rules
The "rules" files should be REPLACED with the new ones, if you want to keep the old ones around then MOVE THEM OUT to another directory NOT INSIDE the "rules" directory, or else they will be run when BFD runs.
If you need apache, proftpd or other "rules" then you will have to modify them yourself, otherwise you should move these out of the "rules" DIRECTORY, they will not do much with BFD set to run every minute (unless you modify them yourself). I only modified the rules I needed for my server, feel free to post your own mods here.
OK enough, here's the file:
[url]
(it's also attached to this message, see below)
This file will only be around for a few months on this free upload site. Someone please put it in a good place/mirror and post a link, thanks.
Technical details:
This runs every minute but keeps a list of the last 10 minutes of bad IPs in a file in tmp, trimming the file every minute so only new IPs are saved.
You can see the list of IPs in files such as: /usr/local/bfd/tmp/.exim /usr/local/bfd/tmp/.sshd
The marker "----" (four dashes) is used to mark each minute and is ignored by BFD but used to trim the old IPs off the file.
If the number of "----" are more than 10, it trims the top of the file up to the marker every run. If the file doesn't exist it's created.
The exim filter "grep" part was modified slightly because the old one was producing bad data every once and a while. The others are all the default filters that come with V0.9.
(BFD people feel free to add this to the next version update, I consider it GPL)
I've ordered 1gbit/s port with one my dedicated servers. But I am still unhappy with the speed of download.
I have 2 mbit DSL connection at home and I can download files with 90 kb/s from the server. I also see the same speed on a 100mbit port server. But I can download files from RapidShare with 210 kb/s..
What do you recommend me to do make faster downloads from server-side?
In a system with all-in-one solution -- WEB, EMAIL, MySQL, FTP..in a same hard-disk.
Would you prefer a "Last Longer" - SATA2 Enterprise Harddisk (Western Digital or Seagate) OR Would you prefer a "Spin Faster" - SATA1 RAPTOR (Western Digital)
So I have been reduced, I am a firm *nix Apache user, to using IIS along with ISAPI for redirection at work. Now I can setup the redirection(s) just fine using the GUI, but I am a *nix man and doing this through the GUI is SLOW! That is when it has to be done on 3 servers at a time plus I can only access those servers through a Citrix environment.
And I need to be adding redirects many times a week. Is there any way to setup ISAPI redirects from a command line? Google has offered me nothing.
I've been working in this industry for 5 years now. Over the years, I've come to realize the little things that customers do that REALLY piss tech support off. This is a guide for customers for 10 things NOT do when contacting their host's technical support team.
This is a repost of what I already posted before the big catastrophe.
Please forgive the brutal honesty. It's for your own good.
1. One ticket per issue. Emailing your issue to Support, Sales, Billing, Abuse, the owner, each individual tech, and the mayor of your town is not going to get your ticket answered any quicker. Additionally, opening 2, 3, 4, or 10 tickets isn't going to get things done any faster. Seriously - all it will do is irritate the support guy
2. Contact the proper department If your account is suspended due to non-payment, or your account hasn't yet been setup, or you want to upgrade your account - please don't bother contacting support hoping it'll get done faster. All it will do is slow down their response time to customers that have actual support issues. Billing issues goto Billing. Sales issues goto Sales. Abuse issues goto abuse. Get the picture?
3. Contact support via ONE medium If you put in a support ticket, don't get on live chat and call too. Trust me - you'll get the same answer on live chat and the phone as you will in the ticket . Same goes for requesting "updates" on your ticket - if your ticket is in queue, wait patiently for a response. If you don't get a timely response, contact the management to complain.
4. Everyone thinks their ticket is CRITICAL Tech support reps realize that you think your issue is CRITICAL and must be dealt with IMMEDIATELY. But, guess what, so does everyone else that submitted their ticket before you. Your CRITICAL ticket will be answered in the order received after everyone else's CRITICAL ticket has been answered.
5. Do not try to "bump" your ticket Making continuous replies to your ticket in an event to get a faster response won't work. In fact, in most common helpdesk applications, each reply made rotates the ticket to the bottom of the queue. So really, by bumping your ticket, you're just making yourself wait longer. Not getting service fast enough? Contact the manager of the company!
6. Include all relevant information, but only relevant information Seriously - we don't care to hear your life story. Submit your ticket with your client ID, domain name, username, password, error messages, steps to reproduce, and other information directly pertinent to your issue. If your website is inaccessible, check http://www.downforeveryoneorjustme.com/ and include your local IP address (from www.whatismyip.com) and a traceroute. That will save you a reply.
7. Just because YOU can't see the website does NOT mean the server is down So please - don't come shouting at us claiming we're fraudsters and have horrible uptime and demand a credit. Most of the time you will find there is either a firewall issue or a routing issue - or scheduled maintenance. Check http://www.downforeveryoneorjustme.com/ and your host's forums before screaming at them.
8. Avoid live chat & phone support Unless you have a quick question, live chat and phone support are probably not going to be good avenues. Chances are, if your issue requires someone to login to the server to investigate, you're just going to be escalated to a support ticket. Instead of whining about how long the support ticket will take to get answered - just get it in queue. Figure if you spend 5-10 minutes on the phone only for them to tell you that you need to submit a ticket - that's 5-10 minutes that your ticket could have been looked into. Think about it. If you do call or chat - be brief - and keep in mind we have other customers to help.
9. We don't make the rules If you don't like a company's policies or procedures, don't complain to your support tech about it. They don't make the rules, they just follow them. If you want a change, contact the management of the company.
10. Do NOT disrespect or mistreat support people If you curse at us, disrespect us, or mistreat us in any way - you can almost be guaranteed that we won't be going out of our way to help you beyond the minimum. By polite, cordial, and courteous to your support tech and it will get you a LOT farther. We don't get paid enough to deal with people's abuse.
11 (Free bonus ). The amount of money you pay does not matter to us Seriously - the fact that you pay us $9.95/month does not matter to us. We're going to provide you with the same support that we provide somebody that's paying $3.95/month or $99.95/month. Don't expect better treatment based on the amount of money you pay.
I've been working in this industry for 5 years now. Over the years, I've come to realize the little things that customers do that REALLY piss tech support off. This is a guide for customers for 10 things NOT do when contacting their host's technical support team.
Please forgive the brutal honesty. It's for your own good.1. One ticket per issue.
Emailing your issue to Support, Sales, Billing, Abuse, the owner, each individual tech, and the mayor of your town is not going to get your ticket answered any quicker.
Additionally, opening 2, 3, 4, or 10 tickets isn't going to get things done any faster.
Seriously - all it will do is irritate the support guy 2. Contact the proper department If your account is suspended due to non-payment, or your account hasn't yet been setup, or you want to upgrade your account - please don't bother contacting support hoping it'll get done faster. All it will do is slow down their response time to customers that have actual support issues. Billing issues goto Billing. Sales issues goto Sales. Abuse issues goto abuse. Get the picture?3. Contact support via ONE medium
If you put in a support ticket, don't get on live chat and call too. Trust me - you'll get the same answer on live chat and the phone as you will in the ticket . Same goes for requesting "updates" on your ticket - if your ticket is in queue, wait patiently for a response. If you don't get a timely response, contact the management to complain.4. Everyone thinks their ticket is CRITICAL
Tech support reps realize that you think your issue is CRITICAL and must be dealt with IMMEDIATELY. But, guess what, so does everyone else that submitted their ticket before you. Your CRITICAL ticket will be answered in the order received after everyone else's CRITICAL ticket has been answered.5. Do not try to "bump" your ticket
Making continuous replies to your ticket in an event to get a faster response won't work. In fact, in most common helpdesk applications, each reply made rotates the ticket to the bottom of the queue. So really, by bumping your ticket, you're just making yourself wait longer. Not getting service fast enough? Contact the manager of the company!6. Include all relevant information, but only relevant information
Seriously - we don't care to hear your life story. Submit your ticket with your client ID, domain name, username, password, error messages, steps to reproduce, and other information directly pertinent to your issue. If your website is inaccessible, check [url] and include your local IP address (from www.whatismyip.com) and a traceroute. That will save you a reply.7. Just because YOU can't see the website does NOT mean the server is down
So please - don't come shouting at us claiming we're fraudsters and have horrible uptime and demand a credit. Most of the time you will find there is either a firewall issue or a routing issue - or scheduled maintenance. Check [url]and your host's forums before screaming at them.8. Avoid live chat
