Don't you think it would be better to export all data and re-import,
rather than go through 5 upgrade steps?
Also my impression was that Juan's question was about the advisability
of moving to 5.0 considering that it's just out and may not be
completely stable yet. Juan - it all depends on your appetite for
risk, enthusiasm for new features, and willingness to do another upgrade
(next year?). You might want to go straight to 5.0, but it is
definitely a fresh release, and likely to have a few point releases over
the next year or so, some of which will include bug fixes, if past
releases are any indication :)
-Mike
On 11/15/2011 1:46 AM, Geert Josten wrote:
Hi Mariano,
I believe the recommended route for such an upgrade would be to
upgrade to the latest version within the 3.2 branch first, upgrade
from there to the latest within the 4.0 branch, upgrade to 4.1,
upgrade to 4.2, and then upgrade to 5.0. Obviously start off with a
backup of your original 3.2 installation..
Kind regards,
Geert
*Van:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]
<mailto:[email protected]>] *Namens *Mariano
Grau Calín
*Verzonden:* maandag 14 november 2011 11:23
*Aan:* General MarkLogic Developer Discussion; General MarkLogic
Developer Discussion
*CC:* Juan Aurelio Pecino Chacón
*Onderwerp:* Re: [MarkLogic Dev General] Decreased performance
afterreindexing database in MarkLogic 3.2
Thanks,
We will undo changes to in-memory tree size and in-memory range index.
Also, will migrate as soon as posible. Do you recomended MarkLogic 5
(just released) or 4?
Mariano Grau
Dpto. Sistemas
Grupo Joly
-----Mensaje original-----
De: [email protected]
<mailto:[email protected]> en nombre de Michael
Blakeley
Enviado el: dom 13/11/2011 23:29
Para: General MarkLogic Developer Discussion
CC: Juan Aurelio Pecino Chacón
Asunto: Re: [MarkLogic Dev General] Decreased performance
afterreindexing database in MarkLogic 3.2
I can make a couple of observations that are valid for every version
of MarkLogic Server to date:
* The changes to in-memory tree size and in-memory range index size
were not a good idea. Higher limits mean larger in-memory stands,
which will increase memory utilization. That is not likely to improve
performance, and may well hurt performance. I would undo those changes.
* The increased database size and memory utilization probably indicate
a large number of deleted fragments, which should be visible on the
database status page. Merge the database to get rid of those.
3.2 is indeed very old now, and I would recommend upgrading as quickly
as is practical. Note that upgrading will require more reindexing. So
I would defer the full merge, recommended above, until after that
upgrade is complete.
-- Mike
On 13 Nov 2011, at 12:32 , Eric Bloch wrote:
> I believe a formal end-of-life notice has been given for MarkLogic 3.2.
>
> -Eric
>
> Eric Bloch
> [email protected] <mailto:[email protected]>
>
>
>
> On Nov 13, 2011, at 11:11 AM, Mariano Grau Calín wrote:
>
>> Hi all:
>>
>> We had to reindexing/refragmenting the database because searchs by
trailing date not working.
>> The new documents was not indexed by date. After reindexing (the
operation takes 40 hours), all works fine. However, searchs by text
that previously took less than a second, now takes between five and
ten seconds. Also, database size increased 30 GB.
>>
>> The database has 12,5 millions documents and 140 GB in two forests.
Run on hp DL385 AMD 64bits Quad Core 2,2 Ghz, 16 GB RAM and one disk
250 GB raid 1 on EVA8000. The operating system is Windows 2003
Standard Edition SP2 and MarkLogic Server 3.2.
>>
>> We modified parameters database for improving performance, now
Marklogic process in memory is 12 GB (before 9,5GB), with not sucess.
>> Before After
>> in memory limit 524288 1048576
>> in memory list size 1024 1024 (máx.)
>> in memory tree size 256 1024
>> in memory range index size 16 64 (máx.)
>>
>>
>> We hope to improve the performance without to buy new hardware and
licens.
>>
>> Thanks and regards,
>>
>>
>> Mariano Grau
>> Dpto. Systems
>> Grupo Joly
>>
>>
>>
>> _______________________________________________
>> General mailing list
>> [email protected] <mailto:[email protected]>
>> http://developer.marklogic.com/mailman/listinfo/general
>
> _______________________________________________
> General mailing list
> [email protected] <mailto:[email protected]>
> http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected] <mailto:[email protected]>
http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general
