Log states: Allowed memory size of xxx bytes exhausted
When this happens, WriteBackExtreme is attempting to load too much data. The extension retrieves records in batches of 1,000 until all rows are fetched. If each row contains a large amount of data or the table has many columns, this process can exhaust the available memory.
The best solution is to limit the amount of data being queried. Ask yourself: Do I really need to load this much data? Often, a slimmer table can serve the same purpose—and will perform significantly better than a large table packed with heavy rows.
If reducing the dataset is not an option, there are two alternatives:
Decrease the number of records loaded per batch (default is 1,000).
Note: This setting applies to all schemas.
You can do this by navigating to the 'Chunk Size' setting within the advanced configuration, and lowering it:
Increase the memory limit by altering the wbe.config.toml file like so:
Note that the indentation in wbe.config.yaml matters! To apply the new memory limit, please restart WriteBackExtreme.
