Making progress...
The index were deleted due to some regression introduced last year when
using alias and not OIDs when creating index.
Another issue is that the master tabl, containing all the entries, was
read fully for each index to create, instead of reading it only once,
and adding the read entries in all the indexes in one operation.
I'm running some more tests before committing the changes.
One suggestion : declare the index, stop the server, restart the server,
then inject the entries. The index will be present and the server won't
try to recreate them when starting, as they will already be present when
you will start to inject the entries. You'll pay the price of injecting
the entries and creating the indexes only once.
More to come...
Le 4/15/12 1:42 PM, [email protected] a écrit :
ok much appreciaed. Thank you!
________________________________________
From: Emmanuel Lécharny [[email protected]]
Sent: Sunday, April 15, 2012 6:32 AM
To: [email protected]
Subject: Re: Update 2.0.0-M7 and indexes
Le 4/14/12 5:12 AM, [email protected] a écrit :
Hi, regarding the server startup issue I'm having after loading a custom
partition with 80k users, the problem seems to be the size of master.db
For my partition. The file is 450 MB. If I delete my partition directory (and
let to recreate on startup) the server starts fine.
Here are some other things we tried, none of which worked.
Don't waste your time doing experiments, tehre is a clear problem in the
index construction when the server is restarted. I'm on it this afternoon.
Seems like the index creation actually works, when we have a few
hundreds of entries, but we have serious performance issues with 80 000
entries.
I'm not sure it's a bug, but certainly some sub-optimal process.
Keep tuned...
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
