Yes, may be controlled by a timer (like FireDac is doing it). Currently I split it into two Pools. One big one full features and a new one small and lightning one for very fast processes like create an image or create json data. The big one killed me in the past very often because my available memory goes down to 0 MB. A BeforeUnlockHandler would be nice, to free own data, which is not longer needed.
Currently the spilitting in different datapools for fat or lighting processes seems to be a good way.
Here you can see two pools: A pool counter (fat) and a json-Poolcounter(lightning).
https://sepla.intercongress.de/0/monitordb
Doing this way also helps to avoid increasing the pools (due to Faster response it is more unlikeley that you need a seconds datamodule)
Also an onRestoreHandler would be nice (for setting up the datamodule with default values)
Currently the spilitting in different datapools for fat or lighting processes seems to be a good way.
Here you can see two pools: A pool counter (fat) and a json-Poolcounter(lightning).
https://sepla.intercongress.de/0/monitordb
Doing this way also helps to avoid increasing the pools (due to Faster response it is more unlikeley that you need a seconds datamodule)
Also an onRestoreHandler would be nice (for setting up the datamodule with default values)
Greetings
Sven
Sven