Xampp 1.7.3 high load upgrade#
Xampp 1.7.3 high load windows 10#
Xampp 1.7.3 high load code#

Turning EnableMMAP to off also has nothing to do with AcceptEx(). No need for it, don't load it, ram saved. The ram hit to it was likely washed away by modulizing darn near everything but the really core features. This is probably the one change that really sped up 2.4. I also find that small files do much better with it turned Off. I find the only way I can have successful large file transfers (with 4GB ram) is to put them in a folder that I can specifically turn EnableSendfile to On for or to use instead. With 4GB of RAM this will likely become noticeable on file transfers over 800MB+/- finishing incomplete. Mileage will vary per system.Īlso note that EnableSendfile's default changed in 2.3.9.ĮnableSendfile On saves RAM but at a cost to speed, probably not so much with an SSD, yet it is 2.2's default so changing this will change Apache's profile. I have a problem with this specific copy and paste reply I see a lot to the AccpetEx() problem because EnableSendfile & EnableMMAP have absolutely nothing to do with AcceptEx() and does have other real world pros & cons that can become beneficial or problematic. Will do exactly the same, just two lines instead of one. What about 2.2's Win32DisableAcceptEx? After all, AcceptEx() is causing a problem, but not the root problem of running out of threads. Just pointing out the fact to others that you're on 2.2, not 2.4. Posted: Fri 30 Aug '19 0:32 Post subject: With that error add the following to your nf file and restart apache Posted: Thu 29 Aug '19 14:55 Post subject: Re: Apache runs out of threads but we're maxed out We're hoping someone here could help shed some light. We've been scouring the web for possible solutions but haven't turned up anything yet.

It's possible but we'd like to keep it to the last resort. A suggestion was made to switch to NGINX but some rudimentary testing shows that the application makes heavy use of Apache URL re-writes and converting them into NGINX Directives would be overly complicated.Ī last resort would be to recode the portion of the application that does the QR scanning. We are unsure if the application will run on PHP 7 or greater and to verify would mean a great deal of testing (and there's no guarantee it would solve the issue).

Xampp 1.7.3 high load upgrade#

The application itself was coded in PHP.ĭue to the nature of the application, our first choice would be to tune or upgrade Apache (in that order).

Xampp 1.7.3 high load windows 10#

Host machine is running Windows 10 and runs XAMPP 1.7.3 which provides Apache 2.2.14, MySQL 5.1.41 & PHP 5.3.1.

Feedback from users seem to indicate this made things worse so we turned it back on. As mentioned, it's currently at 1920 and can't be raised any more.Ģ. : winnt_accept: Asynchronous AcceptEx failed.'ġ. Sometimes when this happens, the following error is also printed to the Apache error log: '(OS 64)The specified network name is no longer available. Consider raising the ThreadsPerChild setting' which is already maxed out at 1920 threads (a warning is printed to the Apache error log if we try to exceed 1920) Apache's error log says 'Server ran out of threads to serve requests. The host machine lags to the point of being unusable forcing a restart to get the application running again. On some occasions, the application stops responding and does not read QR codes. Multiple training sessions are going on simultaneously and most also finish at the same time meaning that there is a large number of trainees scanning their QR codes at the same time.

Xampp 1.7.3 high load code#

Trainees each have a QR code which they scan in the training labs to verify their presence. It's hosted on a Windows 10 machine with an SSD and 4GB of RAM. We inherited maintenance of an old application at a training organization.

Posted: Thu 29 Aug '19 14:38 Post subject: Apache runs out of threads but we're maxed out Topic: Apache runs out of threads but we're maxed out