Monday 27 September 2004 6:55:32 am

Does your PHP module have the <i>MBString</i> extension compiled in?

Without this eZ publish is forced to do the conversion in pure PHP which is a lot slower than the extension and it will also use much more memory.

More info on the PHP mbstring extension can be found here:
http://www.php.net/manual/en/ref.mbstring.php

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Thursday 20 January 2005 11:48:19 am

It would be great to have some response about the Unicode problems with EZ - even with MbString enabled with PHP, memory just disapears and a 450mb Apache is a pretty ugly sight.

It would be nice to see ez.no running Unicode on its own site!

Monday 24 January 2005 1:47:12 am

ezpublish 3.5.0

PHP
Version:
4.3.9
Extensions:
xml, tokenizer, standard, session, posix, pcre, overload, mysql, mbstring, gd, ctype, zlib, openssl, apache2handler
Miscellaneous:
Safe mode is off.
Basedir restriction is off.
Global variable registration is off.
File uploading is enabled.
Maximum size of post data (text and files) is 8M.
Script memory limit is Unlimited.
Maximum execution time is 60 seconds.

PHP accelerator
ionCube PHP Accelerator (enabled)
phpa cache is disabled because of memory leaks (better performance without it)

Apache2

Name:
Apache
Version:
Apache
Modules:
core, mod_access, mod_auth, mod_include, mod_deflate, mod_log_config, mod_env, mod_mime_magic, mod_usertrack, mod_setenvif, mod_ssl, prefork, http_core, mod_mime, mod_status, mod_autoindex, mod_asis, mod_suexec, mod_cgi, mod_vhost_alias, mod_negotiation, mod_dir, mod_imap, mod_actions, mod_speling, mod_userdir, mod_alias, mod_rewrite, mod_so, sapi_apache2

CPU: (dedicated server, no possible changes to hardware)
CPU 2.40GHz (686-class CPU) 2412.08- MHz
Memory:
479.94 MB

Database mysql (last production one 4.)
UTF8 database
Query cache enabled
Thread cache enabled

Running on freebsd (from the root of the tree, no subfolders)

The main problem is with the index cron, wich kills the machine completely and takes very long long time to complete. If we index at the moment of publishing apache takes (depending on the text size) up to 200MB ram, wich kills the server. We need the search engine, but if we cannot index content its useless.
What needs so much memory to run???
Are you putting the whole database on memory??

I think you should know that ez 3.5 has very big problems compiling diferent siteaccess at the same time or when two users load the same page at the same time and it has no cache (template and content). That makes two apache processes grow and grow, and the server...

Thanks

Tuesday 25 January 2005 1:46:34 am

Sorry for the delay i'm very very busy.
Articles are normal articles, not so long, 1 to 3 msword pages aprox. I cannot publish it here, sorry.
Is just words in several languages. With DelayedIndexing=enabled every thing works, but if i disable or run the index cron the server dies.
What is the diference if we publish words, simbols, chinese or whatever, we use unicode, so every thing should be coded in the same way.

Thanks