Apache Server (wamp) What's needed to go to a "production" server? What settings would I change?

I have a test machine running WAMP.. It's an old machine:

Windows Server 2003 OS
AMD Athlon XP 1.29 ghz
1gig ram

It's my webserver from home, but here's the catch... I want to get everything setup on it first, then when I'm ready, replicate everything onto a production server.

Now, I like WAMP a lot, and I'd love to use it on a production server.. I've messed with the my.ini httpd.conf and vhosts to get it working smoothly.  Is there a big downside to using WAMP instead of installing everything separately?

I would like to change my installation to more of a production environment... Is there a certain type of MYSQL setting that I should change that's better quited for this?

For instance.. my server hangs up... it maxes out the CPU 100% when I do a customized zen cart easy-populate export... What I mean by "hangs up" is that I cannot access any webpages served on it while its generating the .txt product export file... I assume if I flip some switches that it will allow for some better "threading"? so that it wouldn't grind to a halt?   My hunch is that WAMP assumes it will be in a test environment and not a production environment, so that I is not setup to accommodate multiple users, rather just 1 user primarily?

Thanks!

BTW I already enabled mysql caching.
www_puertoricoautoforo_comAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
Advertise Here
 
Michael WorshamConnect With a Mentor Infrastructure / Solutions ArchitectCommented:
The reason it does that is because PHP doesn't support multi-threading under Windows platforms. The process control extension is meant for non-web server PHP applications.

Reference:
http://www.php.net/manual/en/ref.pcntl.php
0
 
Michael WorshamInfrastructure / Solutions ArchitectCommented:
WAMP (and XAMPP) for that matter are good for development and learning environments, but not a very stable platform for long-term production use.

Under Windows, processes that use applications (i.e. Apache, MySQL) don't easily clean up after the process is shutdown, thus can cause server environment instability and CPU/memory issues in the long run. Under Linux, however, processes that terminate will release all CPU and memory under said process - the the reason most Linux servers can run for extended periods of time without having to reboot (my personal server has been running for nearly a year without a reboot).

I would recommend setting up a Linux server (either by itself or virtual) and going from there. I, personally, would use CentOS or RHEL as there are RPMs for the Apache, PHP and MySQL environment readily available for download, which - in turn - makes it very easy to deploy and configure.
0
 
www_puertoricoautoforo_comAuthor Commented:
I would but it's too much headache for me to get linux servers working 100%, I'm pretty happy with the Windows 2003 server, actually I haven't had to reboot it much, it just maxes out the CPU when the easy populate process is running, once it's done it's fine again.. I'm just surprised that it doesn't allocate some CPU resources to other php sessions at the same time.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.