could be.
Write is not a fast action now with the mongo driver. Take into account that
each object generates a graph of dictionaries who are committed to the DB.
Depending on the complexity of that graph, you will have larger write times.
you can try measuring time of two separated operations:
[ serialized := VORepository current serializer serialize: theObject ]
timeToRun.
[ VORepository current resolver
insert: theObject
serialized: serialized
withId: OID nextOID ] timeToRun.
that might give you a better idea of what happens (you can also use the
TimeProfiler to see where your time is consumed)
if you have to write such collections in a regular basis, from there you can
explore ways to speed up the process.
Sorry not being able to help more, but the amount of information you give me is
like going to the doctor and say “it hurts!” :P
cheers,
Esteban
> On 03 Apr 2015, at 01:25, Josefina Arcidiacono <josefine2...@hotmail.com>
> wrote:
>
> Hi!
> I'm using Voyage with MongoDB.
> I need to store an object with a large collection.
> Since both are voyageRoot, there is a Mongo table with all the collection
> objects and another with the first object pointing to them.
> With 20,000 objects in the collection it's taking 30 min to save.
> ¿Is that normal?
>
> Josefina
>
>
>
> --
> View this message in context:
> http://forum.world.st/Voyage-performance-issue-tp4817087.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
