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
One way which is compatible with the preallocation philosophy of memory managment is to add a custom memory allocator + manager under AIKR for entry's which are utilized.
"One way which is compatible with the preallocation philosophy of memory managment is to add a custom memory allocator + manager under AIKR for entry's which are utilized."
I agree it's quite space-wasting. Let's see how the stats look like, if the concepts have their implication tables full for most long-term runs it won't help much. While if most of them are quite empty, there will be great benefit of such an allocator. Let's see.
patham9
changed the title
Design: Precondition table needs to much memory with "to many ops"
Design: Precondition table needs to much memory with "too many ops"
Nov 27, 2022
patham9
changed the title
Design: Precondition table needs to much memory with "too many ops"
Design: Precondition table needs too much memory with "too many ops"
Apr 1, 2023
How to reproduce? Set OPERATIONS_MAX to something like 15 or 32.
In Concept.h we have
this causes OOM for machines with <1GB and default config for number of concepts.
The text was updated successfully, but these errors were encountered: