Forums / Install & configuration / eZ publish CMS and Windows production environment.

eZ publish CMS and Windows production environment.

Next topic

Author	Message
Wojciech Potaczek	Wednesday 07 June 2006 4:15:08 am Always we install an eZ publish CMS on Linux environment, but we have a new customer for whom the requirement is a CMS system working on Windows 2003 Server. If we are sure, that a given server has sufficient parameters of equipment to activate specific website on Linux environment, may we use a Windows system to create a production environment for this website? Are there any oppositions connected with stability this solution? (php+apache on Windows, etc). What about the efficiency between both environments (Windows and Linux). Will it be considerable? Should we use Apache 1.3 or Apache 2.0 for Windows environment? Do you have any practical experiences connected with this kind of soultion on Windows 2000 Server? Best regards, -- Wojciech Potaczek
Łukasz Serwatka	Wednesday 07 June 2006 4:41:43 am I would highly recommend latest stable version 1.3 of Apache for Windows and latest version of eAccelerator. Apache 1.3 because of stability and eAccelerator because of performance impact. And the most important is security factor on Windows, you should take care about all updates and proper configuration of Apache, etc. However for maximum performance and stability we recommend Linux environment (Apache, PHP, MySQL and latest version of APC). See also: http://ez.no/community/forum/install_configuration/linux_or_windows_for_ez_publish/re_linux_or_windows_for_ez_publish http://ez.no/community/forum/install_configuration/ez_publish_performance http://ez.no/products/ez_publish/info/requirements_for_ez_publish Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog

Author

Message

Wednesday 07 June 2006 4:15:08 am

Always we install an eZ publish CMS on Linux environment, but we have a new customer for whom the requirement is a CMS system working on Windows 2003 Server.
If we are sure, that a given server has sufficient parameters of equipment to activate specific website on Linux environment, may we use a Windows system to create a production environment for this website?
Are there any oppositions connected with stability this solution? (php+apache on Windows, etc).
What about the efficiency between both environments (Windows and Linux). Will it be considerable? Should we use Apache 1.3 or Apache 2.0 for Windows environment?
Do you have any practical experiences connected with this kind of soultion on Windows 2000 Server?

Best regards,

--
Wojciech Potaczek

Łukasz Serwatka

Wednesday 07 June 2006 4:41:43 am

I would highly recommend latest stable version 1.3 of Apache for Windows and latest version of eAccelerator. Apache 1.3 because of stability and eAccelerator because of performance impact. And the most important is security factor on Windows, you should take care about all updates and proper configuration of Apache, etc.

However for maximum performance and stability we recommend Linux environment (Apache, PHP, MySQL and latest version of APC).

See also:
http://ez.no/community/forum/install_configuration/linux_or_windows_for_ez_publish/re_linux_or_windows_for_ez_publish

http://ez.no/community/forum/install_configuration/ez_publish_performance

http://ez.no/products/ez_publish/info/requirements_for_ez_publish

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

eZ debug

Timing:

Jan 20 2025 08:56:44

Script start

Timing:

Jan 20 2025 08:56:44

Module start 'content'

Timing:

Jan 20 2025 08:56:44

Module end 'content'

Timing:

Jan 20 2025 08:56:44

Script end

Main resources:

Total runtime

0.0218 sec

Peak memory usage

2,048.0000 KB

Database Queries

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0081	590.5391	180.8047
Module start 'content'	0.0081	0.0051	771.3438	93.9766
Module end 'content'	0.0133	0.0084	865.3203	70.7031
Script end	0.0217		936.0234

Checkpoint

Start (sec)

Duration (sec)

Memory at start (KB)

Memory used (KB)

Script start

0.0000

0.0081

590.5391

180.8047

Module start 'content'

0.0081

0.0051

771.3438

93.9766

Module end 'content'

0.0133

0.0084

865.3203

70.7031

Script end

0.0217

936.0234

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0021	9.6435	12	0.0002
Check MTime	0.0010	4.7966	12	0.0001
Mysql Total
Database connection	0.0016	7.3977	1	0.0016
Mysqli_queries	0.0036	16.4453	4	0.0009
Looping result	0.0000	0.0831	2	0.0000
Template Total	0.0081	37.3	1	0.0081
Template load	0.0007	3.0319	1	0.0007
Template processing	0.0075	34.2703	1	0.0075
Override
Cache load	0.0004	1.9440	1	0.0004
General
dbfile	0.0053	24.1185	10	0.0005
String conversion	0.0000	0.0273	3	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Accumulator

Duration (sec)

Duration (%)

Count

Average (sec)

Ini load

Load cache

0.0021

9.6435

0.0002

Check MTime

0.0010

4.7966

0.0001

Mysql Total

Database connection

0.0016

7.3977

0.0016

Mysqli_queries

0.0036

16.4453

0.0009

Looping result

0.0000

0.0831

0.0000

Template Total

0.0081

37.3

0.0081

Template load

0.0007

3.0319

0.0007

Template processing

0.0075

34.2703

0.0075

Override

Cache load

0.0004

1.9440

0.0004

General

dbfile

0.0053

24.1185

0.0005

String conversion

0.0000

0.0273

0.0000

Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	pagelayout.tpl	<No override>	extension/sevenx/design/simple/templates/pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Usage

Requested template

Template

Template loaded

Edit

Override

pagelayout.tpl

<No override>

extension/sevenx/design/simple/templates/pagelayout.tpl

Number of times templates used: 1
Number of unique templates used: 1

Time used to render debug report: 0.0001 secs