[openstreetmap/openstreetmap-website] Integrate the high-performance GPX importer (#1852)

[mmd]

Out of curiosity, what was the main bottleneck motivating the switch to a C implementation?

Inserting gps_points is notoriously slow to the use of single insert, but would probably benefit quite a bit from a bulk insert operation via `activerecord-import `(-> affects https://github.com/openstreetmap/openstreetmap-website/blob/master/app/models/trace.rb#L292-L307). So this part could be covered by some Rails code with decent performance.

I'm not sure if parsing GPX files as such is really an issue. Once I disable `tp.save!` in trace.rb, processing traces via gpx_import.rb is really fast.

The calculation of the `tile` value is already exposed via another Gem (native implementation), and is only duplicated in the GPX importer.

Then there's some image generation which I don't know much about. Could this be the only thing left worthwhile keeping in a native gem?




-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/1852#issuecomment-426634563
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20181003/2d562f69/attachment.html>