You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the comment @sbarzowski made in a different conversation that only the value cache of a VM is affected when variables are changed but not the import AST cache, it led me to think that maybe qbec should be re-using VMs from a pool and not creating them on demand such that existing import caches in the VMs created can provide performance boosts.
For this to work I need a way to clear all variables (TLAs, extvars etc.) since the set of variables is not consistent across VM use. Currently, I think there is no way to do this. Probably a method like ResetVars() on the VM instance which blanks out the exts, tlas and nukes the value cache.
Happy to provide a PR if this makes sense.
The text was updated successfully, but these errors were encountered:
Right now you can add/override previously added ones, but not delete them. So yeah, functions to reset them would be nice. I would go with separate functions for reseting tlas and extvars, because they have different cache policies and can be used differently.
Based on the comment @sbarzowski made in a different conversation that only the value cache of a VM is affected when variables are changed but not the import AST cache, it led me to think that maybe qbec should be re-using VMs from a pool and not creating them on demand such that existing import caches in the VMs created can provide performance boosts.
For this to work I need a way to clear all variables (TLAs, extvars etc.) since the set of variables is not consistent across VM use. Currently, I think there is no way to do this. Probably a method like
ResetVars()
on the VM instance which blanks out the exts, tlas and nukes the value cache.Happy to provide a PR if this makes sense.
The text was updated successfully, but these errors were encountered: