[Vtigercrm-developers] Vlastic Search

[Sutharsan Jeganathan]

Hi Alan

Thanks for the information.

Regarding this point

How about the performance factor while each entity modification Event
> Handler  will attempt to update the Elasticsearch database? (Real time
> indexing)
>

I meant that the CRM connects to an external server (ElasticSearch), which
should be properly handled at after save event.  We have the same issue in
our Xero extension(still not released :) ).  In case of failures or network
issues is there a fall back of real time indexing. If not, that will be an
issue at call center.


Thanks
Sutharsan Jeganathan

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=oa-2200-b>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=oa-2200-b>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Apr 11, 2016 at 3:16 PM, Alan Lord <alanslists at gmail.com> wrote:

> On 11/04/16 10:33, Sutharsan Jeganathan wrote:
>
>> Hi Alan
>>
>> It is a good work and congratulations.
>>
>
> Thank you.
>
> I think the demo crm should have large volume of data to preview the
>> effectiveness.i think this extension is for the CRM instances with
>> larger data volume, correct?
>>
>
> That is a very good point. But we don't have any "safe" data. We have
> tested it on customer's systems with large volumes (> 1m records) but of
> course we cannot put that data on-line for all to see ;-)
>
> I will see if we can obtain some public data that we can use.
>
> How about the performance factor while each entity modification Event
>> Handler  will attempt to update the Elasticsearch database? (Real time
>> indexing)
>>
>
> Yes, there are Event Handlers to do this.
>
> If so, will this good for an extremely busy call center agent who has
>> only few seconds to save a ticket before move to next call?
>>
>
> Should be fine. Elasticsearch itself is _very_ fast and it doesn't take
> very long at all to re-index one record.
>
> How the initial indexing should be done, if there are already million of
>> data?
>>
>
> There is a vtiger scheduler job registered to do this. In testing I was
> able to index 50,000 records within a 15 minute cycle but obviously you
> need to determine if that is something you want to do on a production
> system - the volume is configurable and you can enable and disable the
> front-end search feature so it can be turned off whilst you are indexing
> the majority of you data.
>
> Thanks for the feedback.
>
> Alan
>
>
>
> _______________________________________________
> http://www.vtiger.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20160411/3d24a8d1/attachment-0001.html>