Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High memory consumption when looking far into future #216

Open
JJJ opened this issue Jun 20, 2021 · 2 comments
Open

High memory consumption when looking far into future #216

JJJ opened this issue Jun 20, 2021 · 2 comments
Assignees
Labels
scope-performance General performance code type-task

Comments

@JJJ
Copy link
Contributor

JJJ commented Jun 20, 2021

The farther into the future and the more Events that need to be sequenced is the more memory that is inevitably used. This happens linearly and measurably.

Week of June 15, 2121

jjj-on-2021-06-19-at-20-05-13@2x

@JJJ JJJ added scope-performance General performance code type-task labels Jun 20, 2021
@JJJ JJJ self-assigned this Jun 20, 2021
@JJJ
Copy link
Contributor Author

JJJ commented Jun 20, 2021

When testing with Xdebug enabled, use...

ini_set( 'xdebug.max_nesting_level',        -1 );
ini_set( 'xdebug.var_display_max_depth',    -1 );
ini_set( 'xdebug.var_display_max_children', -1 );
ini_set( 'xdebug.var_display_max_data',     -1 );
ini_set( 'xdebug.cli_color',                 1 );

@JJJ
Copy link
Contributor Author

JJJ commented Jun 20, 2021

For context, this isn't actually unexpected or a bug, so much as a lack of caching.

There is no persistent caching for any of the sequence processing, which results in every Calendar view rebuilding all sequences on every page load. This happens through a series of nested loops, and these loops will take more cycles the farther into the future that they need to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope-performance General performance code type-task
Projects
None yet
Development

No branches or pull requests

1 participant