• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved [17.8.11 Update #30] - enable keep-alive

futureweb

Regular Pleskian
Hey there,
how can I enable keep-alive on a specific Hosting in Plesk Onyx?
nginx is deactivated - just apache is used!

already tried:
<ifModule mod_env.c>
SetEnv KeepAlive On
SetEnv KeepAliveTimeout 100
SetEnv MaxKeepAliveRequests 500
</ifModule>

<ifModule mod_headers.c>
Header unset Connection
Header set Connection keep-alive

Header unset Keep-Alive
Header set Keep-Alive timeout=100,max=500
</ifModule>

But it still sends "close" on Connection ....:

upload_2018-11-21_18-41-24.png

keep-alive test telling me it's deactivated: Is Keep-Alive Enabled Checker

any ideas on that?

thx, bye from Austria
Andreas Schnederle-Wagner
 
IgorG - and once again you made me look stupid o_O
Searched quite some time for this Info and wasn't able to find it (always found the WINDOWS Plesk only Version of it) ... thank you! ;-)

keep-alive is now enabled - also some other things like Browser-Caching, GZIP, ...

But sometimes the Site in Question still has a VERY BAD TTFB - escpecially when it's called the first time after it hasn't been called for a few minutes. On the second load the TTFB is ok ... (browser caching disabled of course)
Are there any more tweaks you could think of for enhancing TTFB on initial Page Load?
(seems like apache or php 7.2 is slow spawning the first time it's called?!?)

Site in Question: EDV Dienstleister Fieberbrunn und Umgebung - EDV Service von Profis

Andreas
 
Last edited:
1. Call: Start transfer time: 1.563
[root@localhost animGif]# curl -s -w '\nLookup time:\t\t%{time_namelookup}\nConnect time:\t\t%{time_connect}\nSSL handshake time:\t%{time_appconnect}\nPre-Transfer time:\t%{time_pretransfer}\nRedirect time:\t\t%{time_redirect}\nStart transfer time:\t%{time_starttransfer}\n\nTotal time:\t\t%{time_total}\n' -o /dev/null Sorglos IT Formular - EDV Service Rieseberg

Lookup time: 0.125
Connect time: 0.151
SSL handshake time: 0.357
Pre-Transfer time: 0.357
Redirect time: 0.000
Start transfer time: 1.563

Total time: 1.585

2. Call:Start transfer time: 0.649
[root@localhost animGif]# curl -s -w '\nLookup time:\t\t%{time_namelookup}\nConnect time:\t\t%{time_connect}\nSSL handshake time:\t%{time_appconnect}\nPre-Transfer time:\t%{time_pretransfer}\nRedirect time:\t\t%{time_redirect}\nStart transfer time:\t%{time_starttransfer}\n\nTotal time:\t\t%{time_total}\n' -o /dev/null Sorglos IT Formular - EDV Service Rieseberg

Lookup time: 0.125
Connect time: 0.145
SSL handshake time: 0.343
Pre-Transfer time: 0.343
Redirect time: 0.000
Start transfer time: 0.649

Total time: 0.669

Time is cut in half on second request. Unfortunately it's no Web-Page from us - our Hosting Customer just told us "the Page is slow on our Server and fast on other Servers" ... that's why I started investigating ... if it's really a Server issue of our Shared Hosting Server. Or if it's just the Page which is slow.
Will do some further Tests.

thx
 
Back
Top