It's what community is all about. I'll let you know if we have
problems with it, but so far we are up to 500K records. We started an
average of 13M per index and are at 15M per index, I am hoping it
stays bellow 20M. From what I hear they already have the fix, someone
wrote an entire garbage collection system, and it's already in the
next 5.x release, but until there's an RC for it, I am not going near
it.
James
On Jul 3, 2008, at 12:41 AM, Carl Vondrick wrote:
>
> Thanks for your research on this James. Hopefully the PHP team will
> fix
> these memory issues soon!
>
> On Thu, Jul 03, 2008 at 12:08:01AM -0400, James wrote:
>>
>> We had the same problems, my co-worker managed to find the solution
>> today. The problem stems from bad garbage collection in the current
>> version of php and versions less than that. I asked questions on the
>> propel board and was pointed at about 10 different articles all
>> pointing to that as the problem. Php is suppose to have a fix in the
>> next version 5.x version, but that's not expected for a few months.
>>
>> Our solution is a custom destruct method we had all the Models that
>> were being indexed extend from this custom class, all the problems we
>> had went away, including our indexing of 1.4M records from the
>> command
>> line. We are indexing now and averaging 15MB of memory used for each
>> index. before at this point it climbed up to 1GB (which I had set
>> the
>> server too to see if it would just keep going). We had problems with
>> indexing reviews, when a new review was added when the db contained
>> the 1.4M records, smaller sets of the data 5000 records worked ok.
>> Just lots of memory issues all around. Hope the code helps.
>>
>> James
>>
>> abstract classYourBaseObject extends BaseObject
>> {
>> public function __destruct()
>> {
>> foreach ($this as $index => $value)
>> {
>> if (is_object($this->$index))
>> {
>> if (method_exists($this->$index, "__destruct"))
>> {
>> $this->$index->__destruct();
>> }
>> else if (get_class($this->$index) == "Criteria")
>> {
>> $this->$index->clear();
>> }
>> }
>> unset($this->$index);
>> }
>> }
>> }
>>
>>
>>
>> On Jun 30, 2008, at 6:01 PM, Carl Vondrick wrote:
>>
>>>
>>> On Mon, Jun 30, 2008 at 02:39:48PM -0700, Cristiano wrote:
>>>> I installed the sfLucenePlugin and added the Propel behaviours as
>>>> described in the manual. Everything works (I can create an index on
>>>> the command line, and then search) but when I use actions to create
>>>> new objects, the on-the-fly indexing goes dead slow and times out.
>>>> It's really weird because building a new index from the command
>>>> line
>>>> on the 10 records goes extremely fast.
>>>
>>> Can you provide more information? Can you give me a reproduceable
>>> test
>>> case? What are your system specs? Are you using the production
>>> environment or dev?
>>>
>>> Carl
>>>
>>>>
>>
>>
>>>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
