--
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your ticket NOW - http://www.cfcamp.org/
---
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/bfc25027-b129-4093-9bd6-b9543436f49b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "Lucee" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/lucee/yzWC_lprk6U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/etPan.560d5c94.6d4d7e7e.1244d%40jonclausen-mbp.local.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAPJegvrvPGShcg8w1YZfVTjGk_-bOt9kfBE2gwgg8FnwDX4JpA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/etPan.560d81d1.88f59e6.1244d%40jonclausen-mbp.local.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAPJegvqff3q%2BNZkJSzWYqhSCCpQr003pFVFNHSFZBz%2BxNf4MiA%40mail.gmail.com.
Fwiw David we had the same issue linking elasticsearch to orm/mysql and in the end we rolled our own solution.
We use a combination of triggers, a mysql http udf, rabbitmq with a restful http proxy written in go, and java workers to process the data into elasticsearch.
Sounds complicated but it's been reliable even when we hit thousands of writes per second
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAPJegvqff3q%2BNZkJSzWYqhSCCpQr003pFVFNHSFZBz%2BxNf4MiA%40mail.gmail.com.
On Oct 1, 2015 6:42 PM, "David Sedeño" wrote:
> We need that this updates fires the model orm 'postupdate' event so I need to apply transactions individually
Are you saying that if you put 2, or 10 or more updates in one transaction it doesn't work? If so, wouldn't that be a bug that needs fixing? If not, what is the performance of that?
Jochem
On Oct 6, 2015 9:34 AM, "David Sedeño" wrote:
> 2015-10-05 14:14 GMT+02:00 Jochem van Dieten:
>> On Oct 1, 2015 6:42 PM, "David Sedeño" wrote:
>> > We need that this updates fires the model orm 'postupdate' event so I need to apply transactions individually
>>
>> Are you saying that if you put 2, or 10 or more updates in one transaction it doesn't work? If so, wouldn't that be a bug that needs fixing? If not, what is the performance of that?
>
> More updates in one transaction works, but I have read somewhere that the events in an orm model doesn't fires in ormexecutequerys, only in individual transactions.
So put more updates in one transaction without ormexecutequery.
> And doing individually in a loop of thousands the performance degraded in time. Maybe this could be improve.
Maybe. But I would say the first part of that work is you proving this is:
- caused by Lucee and not an external system like the database or whatever index you are updating in the event handler;
- not caused by a coding pattern which does excessive commits causing I/O overload.
Jochem