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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: brett[at]bretth.com [Submitted to the original trac issue database at 2.29am, Sunday, 28th December 2008]
The pgsql tasks currently have an in-memory geometry option which performs way geometry calculations in java instead of using the database. This currently uses a temporary file which consumes approximately 2.5GB. 2.5GB will fit in RAM on modern machines with 64-bit JVMs so a true in-memory option may provide significantly improved performance.
The text was updated successfully, but these errors were encountered:
Author: brett[at]bretth.com [Added to the original trac issue at 12.16pm, Thursday, 1st January 2009]
The new in-memory options have been implemented. Performance is excellent but requires a system with approx 6G RAM and a jvm setting of -Xmx4G to work effectively.
Reporter: brett[at]bretth.com
[Submitted to the original trac issue database at 2.29am, Sunday, 28th December 2008]
The pgsql tasks currently have an in-memory geometry option which performs way geometry calculations in java instead of using the database. This currently uses a temporary file which consumes approximately 2.5GB. 2.5GB will fit in RAM on modern machines with 64-bit JVMs so a true in-memory option may provide significantly improved performance.
The text was updated successfully, but these errors were encountered: