First, thanks for the quick reponse.
Le 11:19 2006-01-10, vous avez écrit:
At 17:09 10.01.2006, Nicolas Belisle wrote:
Hi,
Here's our production environment :
Windows Server 2005
2Gig RAM
2 x 3.4 MHz
---------------------
Jahia 4.05
1849 pages
We experience two problems with the search engine :
- Its seems the content of many public pages is not indexed.
Strange. Do you have more information about the problem? Which kinf of
page, which kind of information?
It is text information in new pages and modified pages.
- The re-indexing takes more than 20 hours !
Why not simply upgrading to Jahia 4.1? There was a major refactoring of
the re-indexation utility in there which now run as a back-end task + a
few optimization...
I will look into it.
Internally, we use Lucene for a document management system and indexing
around 20 000 pages of text (coming from a database and the filesystem)
takes minutes...
Our caches are currently saturated. Tomcat takes 1,2 Gig of RAM.
Here's our cache configuration :
max_cached_HTMLCache = 2500
max_cached_ContainerCache = 30000
max_cached_ContentContainerCache = 35000
max_cached_ContentFieldCache = 250000
max_cached_FieldIDsByContainerCache = 50000
max_cached_LockPrerequisitesResultMap = 25000
max_cached_TextFileCache = 15000
I've notice some tables with a high number of rows :
The "jahia_acl" tables counts over 350 000 rows.
The "jahia_ctn_entries" tables counts over 45 000 rows.
The "jahia_link" tables counts over 60 000 rows.
Any suggestions would be greatly appreciated.
Migrating to some kind of 64 bit hardware server with more memory (no more
1.5 GB RAM limit for JVM on 64 bit servers) is not possible I presume?
Stéphane
This not an option. We just bought the server for Jahia :)
Is it normal for a production environment to need so much cache, for less
than 2000 pages ?
It is possible that unused containers can pollute pages (coming from
successive modification of pages) ?
Regards,
Nicolas
Thanks,
Nicolas
