You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pipeline for getting other types of geometries into LibGEOS seems to do heaps of allocations - first to nested vectors, then to geos objects. During those allocations there are a lot of slow checks.
To e.g. convert one linestring to a geos linestring we should do one single allocation and write the values without all the checks.
The text was updated successfully, but these errors were encountered:
rafaqz
changed the title
Performance optomise conversions
Performance optimise conversions
Jan 28, 2023
The pipeline for getting other types of geometries into LibGEOS seems to do heaps of allocations - first to nested vectors, then to geos objects. During those allocations there are a lot of slow checks.
To e.g. convert one linestring to a geos linestring we should do one single allocation and write the values without all the checks.
The text was updated successfully, but these errors were encountered: