Skip to content

Pre-emptive transaction cache flush causes severe performance issues #524

@rwgdrummer

Description

@rwgdrummer

The ContentFeatureStore creates a new 'Writer' for each feature added rather than using the same 'Writer', calling 'next'. GeoWaveWriter/GeoWaveReader flush transactions upon creation. Thus, a transaction is flushed for each feature.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions