Hi Kevin,
SQL UPDATE brings some overhead. To have best numbers I suggest you to
execute this operation via Java API:
ODocument day = ..
ODocument hour = ...
List<ODocument> hours = day.field("hours");
hours.add(hour);
day.save();
On 24 October 2014 14:02, Kevin Daly <[email protected]> wrote:
> I using ideas expressed in the time series use case listed below.
>
> https://github.com/orientechnologies/orientdb/wiki/Time-series-use-case
>
> I have a case where I I've broken down the graph by the hour in my time
> series graph, but updating the logs links is having a huge impact on
> performance.
>
> for every log insert I need to update the hour record to add the link to
> the LINKSET with this update
>
> update <RID> add logs =<RID>
>
> If I don't do this update to update the link to the hour object, I am
> getting approximately 11,000 events per second.. Once I add in this update,
> I end up lowering this to about 700 to 800 events per second.
>
> I am currently looking at processing 5000 events per second so in one hour
> there would be 18,000,000 RID's stored per hour block.. Is this practical?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
