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

cache issues #163

Open
jpmorgan98 opened this issue Feb 21, 2024 · 3 comments
Open

cache issues #163

jpmorgan98 opened this issue Feb 21, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@jpmorgan98
Copy link
Collaborator

jpmorgan98 commented Feb 21, 2024

Unknown behaviors and bugs of new cache feature

  • cache work flows before sending to MPI ranks
  • Size of saved cache growing unbounded
  • cache requiring recompilation for altered meshes, census time, and census bank buffer
@ilhamv
Copy link
Collaborator

ilhamv commented Feb 23, 2024

After running in Numba mode and getting the compilation cached, we sometimes want to run in pure Python mode again (e.g., to do Python profiling, to compare Python and Numba error messages, etc). Currently, it seems that cached compilation will be used even if we run in Python mode. Is it possible to bypass or ignore the cached compilation in pure Python mode? @jpmorgan98

@jpmorgan98
Copy link
Collaborator Author

This is very odd behavior. Like even if it's in Python mode it will run as if in Numba? My only thought is to delete the cache folder all together. It should be in /__pycache__ in your execution directory

@jpmorgan98 jpmorgan98 added the bug Something isn't working label Feb 29, 2024
@ilhamv
Copy link
Collaborator

ilhamv commented Mar 5, 2024

It is found that, since we only put the cache decorator in the loop.py, if we make changes in kernel.py, the cache will not recompile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants