...
These cached results are subject to a limit on the number of records cached, but in previous releases
- this limit was only applied to previous cached
...
- results, never to the result just read, and
- if the pipe Cache Size was blank, no limit was applied.
This could result in reading too many records into memory, resulting in excessive garbage collection and loss of service.
At this release,
- there is always an effective pipe Cache Size; if the Cache Size on the pipe is blank, the System Configuration Default Pipe Cache Size is used.
- The pipe Cache Size limit is applied as the result records are being read into memory.
- There is an overall Maximum Pipe Cache Size in System Configuration; setting the pipe Cache Size greater than the maximum will cause the lookup to fail with an error.
- There is an Enforce Pipe Cache Size check box in System Configuration. If checked, pipes that exceed their cache sizes will fail with errors; if not, they will generate warnings.
| Warning |
|---|
If you have migrated from an earlier version of PhixFlow, Enforce Pipe Cache Size is set to unchecked so that incorrect pipe Cache Size settings do not cause existing models to fail. We recommend that you correct the pipe Cache Size settings using the generated progress and warning messages as a guide and set Enforce Pipe Cache Size to checked at the earliest opportunity. |
...