Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Linux » Keepalive Settings: Understanding keepalive configuration

Keepalive Settings: Understanding keepalive configuration

Posted on 19/10/202031/08/2023 Christian By Christian No Comments on Keepalive Settings: Understanding keepalive configuration
Network protocols

The keepalive utility helps to manage web traffic and optimize the use of system resources. With the increase in the number of internet users, the workload on web servers also increases.

The system administrator hence, has to ensure the server is capable of putting up and accommodating the number of connection requests. If the number of users accessing the server increases, the whole system may begin to slow down in terms of access speed; it will become necessary at this point to perform routine tcp tuning on a Linux system. This is where the keepalive utility comes into play

Basically, the keepalive keeps a webpage active for a specified period of time after the user has abandoned it. When there is a high volume of users on a server, a decrease in the timeouts on a tcp socket will hence clean up the connections from the clients that are no longer active.

However, when the server is not busy, the default settings for the keepalive utility should be adequate. There are a couple of other parameters defined that I will explain a little later. This utility kills the connection to the server after completion of each client request. With Keepalive utility, it is possible to use the same tcp connection for all the http requests.

Keepalive Configuration


The following is the default configuration of the keepalive utility:

tcp_keepalive_time = 7200
tcp_keepalive_intvl = 75
tcp_keepalive_probes = 9

[all the above values are measured in seconds except the keepalive_probe which is just a number value]

  1. Keepalive_time: this refers to the time of a connection’s inactivity before a keepalive probeis sent.
  2. Keepalive_interval: this refers to the wait time before another keepalive probeis sent.
  3. Keep_alive probes: this is the number of probes that will be sent before the connection is terminated.

Now according to this default setting, our setup will detect an idle in connection in

[7200 + (75 * 9)] seconds = 7,875seconds.
By default, keepalive is not active on a Linux system. To setup,

Keepalive Setup


1. Activate the keepalive tool. By default is off. To activate it, open up the apache configuration file at /etc/httpd/conf/httpd.conf and include the following:

KeepAlive on

2. Open the /etc/sysctl file with your editor and put in the following values:

net.ipv4.tcp_keepalive_time = 30
net.ipv4.tcp_keepalive_intvl = 5 net.ipv4.tcp_keepalive_probes = 6

Connection maintenance

The values you choose to use are entirely up to you. It should not be too little or too much if your website’s traffic is much.             

3. Now save and quit the editor. Use sysctl –p to apply these changes to your configuration.

And you are done. Now, there are a couple of sites you can test your set up’s efficacy in terms of understanding keepalive configuration (I am not going to advertise for them). All they require is the name of your website. You can also use a tool such as GTMetrix to check your settings.


In summary,


The keepalive utility helps reduce load time on a server when there are multiple requests on the server. To enhance website performance amid heavy traffic, consider utilizing the keepalive utility. This involves understanding keepalive configuration for efficient server-client communication. After enabling it, it automatically opens and closes connections by itself, depending on usage.

However, if you are using a shared hosting provider, there is the likelihood that it will slow down your server.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Linux Tags:TCP/IP

Post navigation

Previous Post: Linux Machine: Is it Virtual or a Physical server
Next Post: All available Policies for the latest version of Microsoft Edge

Related Posts

  • google sdk feature
    How To Install Google Cloud SDK on a Linux System Linux
  • selinux in production
    How to locate directory file context and restore it with SELinux Linux
  • Slide2 3
    Sudo Error on Ubuntu: Fixing ‘unknown uid 1000: Who are you?’ Linux
  • image 129
    Using Awx to deploy, schedule and run playbooks Linux
  • FEATURE IMAGE BASE URL 1
    How to solve cannot find a valid base URL for repo: base/7/x86_64 Linux
  • Screenshot 2020 05 14 at 17.47.09
    Configure OpenSSH Server: A Quick Guide Linux

More Related Articles

google sdk feature How To Install Google Cloud SDK on a Linux System Linux
selinux in production How to locate directory file context and restore it with SELinux Linux
Slide2 3 Sudo Error on Ubuntu: Fixing ‘unknown uid 1000: Who are you?’ Linux
image 129 Using Awx to deploy, schedule and run playbooks Linux
FEATURE IMAGE BASE URL 1 How to solve cannot find a valid base URL for repo: base/7/x86_64 Linux
Screenshot 2020 05 14 at 17.47.09 Configure OpenSSH Server: A Quick Guide Linux

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • fixzoomaudioissue
    How to fix unable to access microphone on Zoom JIRA|Confluence|Apps
  • mdtxxxxx
    Failed to run the action install Operating System: Lifetouch deployment failed, Return Code = -2147467259 0x80004005 when installing Windows image via MDT Windows
  • windows 10 keyboard shortcut 1024x512 1
    How to create a Desktop shortcut in Windows Windows
  • Remote desktop
    Is RDP enabled? Enable and disable Remote Desktop in Windows 10 for all users or selected users Windows
  • Migrate from SQL Database
    Migrate Veeam One Database from SQL Server 2017 to 2025 Backup
  • slide office 365 79
    Configure WSUS Email Notification for Office365 Windows Server
  • How to Enable or Disable Inherited Permissions for Files and Folders in Windows
    How to Enable or Disable Inherited Permissions for Files and Folders in Windows Windows
  • Mendeley Error Code ACLx80sr
    Fix Mendeley Cite Error has occurred: ECITE40001 (ac1x80sr) JIRA|Confluence|Apps

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,811 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.