|
|
|
| Re: [CDO] asynchronous auditing to improve performance [message #1114415 is a reply to message #1114395] |
Sun, 22 September 2013 18:05  |
|
Am 22.09.2013 19:34, schrieb Erdal Karaca:
> I avoided being store specific as I think this should be a feature that could be generally available. Or are you
> saying this is possible with the DBStore already and is missing in the HibernateStore?
I asked because I know that the HibernateStore uses different sets of tables for the latest and the auditing data. So,
there it would likely make sense in terms of the development cost. The DBStore works differently and I can not imagine
anyone would want to spend months to apply this minor optimization there. At least noone has complained about the
DBStore's auditing mode performance since we offer optimized range-based list mappings.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
>
> Eike Stepper wrote on Sat, 21 September 2013 04:17
>> Am 20.09.2013 20:04, schrieb Erdal Karaca:
>> > If auditing is not needed instantly, i.e. if an object is modified, its history will not be inspected instantly,
>> but > "later" (maybe hours or days later).
>> > As the performance decreases with auditing on and growing audited tables, it would be great if auditing could run >
>> asynchronously (in a background job/task) which should not affect CDO's performance seriously.
>> > This would be similar to log4j's capability to log asynchronously.
>> I guess you're talking about the specific auditing support in the HibernateStore?
>>
>> Cheers
>> /Eike
>>
>> ----
>> http://www.esc-net.de
>> http://thegordian.blogspot.com
>> http://twitter.com/eikestepper
>
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.01638 seconds
] 
Search
Help
Register
Login
Home
