I installed varnish on a hello world application, along with nginx, hhvm and mongodb.
The only things that bugges me is that the first time when I access the url I get around 125 ms response time and if I refresh the website again within the next 5 seconds I get around 60-70 ms.
If I wait more than 5 seconds to refresh I get again around 125 ms, but if I remove varnish and relay only on nginx, I get 60-70 ms all the time.
Any thoughts why this is happenig? I am using Varnish 4.0.3
Related
We have spent several weeks trying to fix an issue that occurs in the customer's production environment and does not occur in our test environment.
After several analyses, we have found that this error occurs only when one condition is met: processing times greater than 3600 seconds in the API.
The situation is the following:
SAP is connected to a server with Windows Server 2016 and IIS 10.0 where we have an API that is responsible for interacting with a DB use by an external system.
The process that we execute sends data from SAP to the API and this, with the data it receives from SAP and the data it obtains from the DB of the external system, performs a processing and a subsequent update in the DB.
This process finishes without problems when the processing time in the API is less than 3600 seconds.
On the other hand, when the processing time is greater than 3600 seconds, the API generates the response correctly, and the server tries to return the response to SAP, but it is not possible.
Below I show an example of a server log entry when it tries to return a response after more than 3600 seconds of API processing. As you can see, a 995 error occurs: (I have censored some parts)
Any idea where the error could come from?
We have compared IIS configurations in Production and Test. We have also reviewed the parameters of the SAP system in Production and Test and we have not found anything either.
I remain at your disposal to provide any type of additional information that may be useful for solving the problem.
UPDATE 1 - 02/09/2022
After enabling FRT (Failed Request Tracing) on IIS for 200 response codes, looking at the event log of the request that is causing the error, we have seen this event at the end:
Any information about what could be causing this error? ErrorCode="The I/O operation has been aborted because of either a thread exit or an application request. (0x800703e3)"
UPDATE 2 - 02/09/2022
Comparing configurations from customer's environment and our test environment:
There is a Firewall between SAP Server and IIS Server with the default idle timeout configured for TCP (3600 seconds). This is not happening in Test Environment because there is no Firewall.
Establishing a Firewall policy specifying a custom idle timeout for this service (7200 seconds) the problem will be solved.
sc-win32 status 995, the I/O operation has been aborted because of
either a thread exit or an application request.
Please check the setting of minBytesPerSecond configuration parameter in IIS. The default "minBytesPerSecond" is 240.
Specifies the minimum throughput rate, in bytes, that HTTP.sys
enforces when it sends a response to the client. The minBytesPerSecond
attribute prevents malicious or malfunctioning software clients from
using resources by holding a connection open with minimal data. If the
throughput rate is lower than the minBytesPerSecond setting, the
connection is terminated.
I have a Nuxt.js server side website deployed on Vercel. I've noticed that, on some occasions, I get a 504: GATEWAY_TIMEOUT error, with the code FUNCTION_INVOCATION_TIMEOUT and the message "This Serverless Function has timed out".
Why am I seeing this error?
Vercel imposes some limits when using their platform. This includes a serverless function execution timeout, which is basically the amount of time that a serverless function is allowed to process an HTTP request before it must respond.
Recently, they have silently reduced the serverless function execution timeout from 10s for the hobby plan, 60s for the pro plan and 1000s for the enterprise plan to, respectively, 5s, 15s and 30s. This might be the reason why you're experiencing this error now.
I really didn't like the fact that they lowered these limits without warning their users (I wasn't warned, at least) and giving them time to adjust.
As of 7 September 2022, the Hobby plan on Vercel supports Serverless Function Execution Timeout for 10 seconds. Pro for 60 seconds. Enterprise for 900 seconds.
Here is a link to their pricing plans: https://vercel.com/pricing
Application Error
The request for a Serverless Function reached the timeout threshold (5 seconds for Hobby accounts, 15 seconds for Pro accounts, and 30 seconds for Enterprise accounts). This is an application error.
Getting worse ...
I have a VPS server with Linode. At first it was very fast but now it takes upto 23 seconds to load a webpage. This is so appalling. I have tried configuring Apache and MySQL key buffer but all to no avail. Can I get a standard VPS configuration.
My VPS is a Linode 16GB Ram with 320GB SSD. According to google analytics, I get to 2,073,000 page views per month. What proper configuration do the server need to be fast? And how can I increase server response time (currently, google pagespeed says the server response time is 1.2 seconds and this is very slow.) this has been a great challenge to me.
maybe mainserver is overloaded by other vms i would test the Server with some tools, like test the Speed of copy data.
btw for 80$ i would buy me a real server
Intel® Xeon® Gold 6140
64 GB DDR4 RAM (ECC)
14 dedizierte Kerne
240 GB SSD / 2,0 TB SAS
52$ Netcup for example
if u like stay on the server would be good to know which software ur using, sometimes the mistake is somewehre else, like my page had a loadtime of 16 seconds(i forgot 2 index keys in the db to set)
I have an .exe and webapi projects. When I am calling the webapi from the .exe, the connection force fully closed around 5 mins. But I have set the timeout for HttpClient is 3600 seconds. If we set the timeout below 5 minutes then .exe waits till the time and will get timeout. but if we give more than 5 mins then .exe is not waiting till the time we added. Can any has any suggestion on this? in fact we tried with HTTPWebrequest instead HttpClient but facing the same problem.
Thanks in advance
I have a VPS with 2GB with cPanel/WHM
Installed PHPList Latest Version
Create a batch of 2000 list
PHPList Settings as following
define('USE_DOMAIN_THROTTLE',0.2);
define('DOMAIN_BATCH_SIZE',800);
define('DOMAIN_BATCH_PERIOD',120);
Still it's not sending emails more than 300 taking too much time
A process for this page is already running and it was still alive 532 seconds ago
Sleeping for 20 seconds, aborting will quit
A process for this page is already running and it was still alive 593 seconds ago
Sleeping for 20 seconds, aborting will quit
Started
Processing has started, 1 message(s) to process.
Please leave this window open. You have batch processing enabled, so it will reload
several times to send the messages. Reports will be sent by email to
xxx#yahoo.com
Processing message 79
Looking for subscribers
Found them: 1392 to process
Sending in batches of 10000 emails
I loaded the phplist on my vps having 1gb ram, 20gb hdd, 1 core, ubuntu (lamp, sendmail) and it is running as I answer this. I did not enabled/tweaked any of the above settings. Left as it is. Well there are some issues if the batch size is more than 1000 mails and process q is taking some time if we do not enable domain throttling. Check processing queue in config_extended.php file and it might help in q processing better as they say.
Also check
http://docs.phplist.com/ProcessQueueInfo.html
I also suggest - using phplist with an smtp server (installed on the same vps) or smtp relay. That gives you better mail sending.
might help you
Good Luck
Following are copied from the process...
Started
Processing has started,
One campaign to process.
Please leave this window open. phpList will process your queue until all messages have been sent. This may take a while
Report of processing will be sent by email
Processing message 8
Looking for subscribers
Found them: 6594 to process
Sending in batches of 1000 emails
Processing batch of: 1000
Size of HTML email: 4Kb
Processed 188 out of 6594 subscribers
Script stage: 5
187 messages sent in 60.05 seconds (11210 msgs/hr)
Finished this run
Less than batch size were sent, so reloading imminently
This batch will be 923 emails, because in the last 30 seconds 77 emails were sent
Processing batch of: 923
Size of HTML email: 4Kb
Processed 183 out of 6407 subscribers
Script stage: 5
182 messages sent in 60.07 seconds (10906 msgs/hr)
Finished this run
Less than batch size were sent, so reloading imminently