Re: [geomesa-dev] Ingest performance issues with newest version of geome

[Anthony Fox <anthonyfox@xxxxxxxx>]

Blake,

We recently switched from a text based encoding to an Avro binary encoding.  This should have actually sped up your ingest significantly - it performed very well in tests we ran during development of the binary encoding.  As a point of reference, we have been able to ingest (on a 21 node cluster) about 500K records per second using a map/reduce job.  Can you give a bit more detail about how you are performing your ingest?

Thanks,
Anthony

On Wed, May 28, 2014 at 12:48 PM, Peno, Blake <Blake.Peno@xxxxxxxxxxxxxxx> wrote:

Hi all,

 

I recently upgraded to the newest version of geomesa on github, and I’ve noticed that my performance has drastically dropped in regards to pushing features to geomesa. At this rate it’s going to take about a week to get all of my data uploaded. Has something changed that would cause this, or am I missing something simple?

_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
http://locationtech.org/mailman/listinfo/geomesa-dev